XUUNITY FIX CONTRACT FOLLOWUP PROMPT TEMPLATE

# XUUnity Fix Contract Follow-Up Prompt Template

Use this public-safe template to run an evidence-based review cycle after real
`xuunity fix` sessions expose possible protocol gaps.

The goal is to improve the reusable public `xuunity fix` contract only when
real incidents show a repeated contract problem. Do not change public protocol
rules from one ambiguous session unless the triage clearly proves a protocol
failure.

## Public / Host-Local Boundary

This template is public. The evidence it consumes is host-local.

Keep concrete incident reports, replay results, dated baselines, project names,
customer details, private paths, logs, and generated review outputs outside
public `AIRoot`. A host repo can keep them under its own output root, commonly:

- `<host-output-root>/Reports/System/`
- `<host-output-root>/Reports/System/Smoke/`

When using this template, replace every placeholder with a host-local path:

- `<incident-feedback-template-path>`
- `<incident-report-path-N>`
- `<current-fix-contract-baseline-review>`
- `<current-fix-contract-replay-or-smoke-evidence>`
- `<follow-up-review-output-path>`
- `<self-evaluation-output-path>`
- `<single-incident-output-path>`

## When To Use This

Use it when:
- you have suspicious real `xuunity fix` sessions
- you want to decide whether the public contract needs a small correction
- you have enough evidence to compare real incidents against current expected behavior

Do not use it for:
- one-off brainstorming
- broad roadmap planning unrelated to the `xuunity fix` contract
- private project-code debugging where the public protocol behaved correctly
- publishing host-local evidence into public `AIRoot`

## Prerequisites

For a full follow-up review, collect:
- 3-5 real protocol incident reports created from `<incident-feedback-template-path>`
- the current approved fix-contract baseline review
- the current replay, smoke, or other validation evidence for that baseline

For a single-incident triage, one suspicious session is enough.

## Mode 1: Follow-Up Review

Use this when you want the smallest next protocol fix after several real
incidents.

Template: