x-harness-admissionlisted

# x-harness-admission Use this skill when you need to create, update, or verify a completion claim in a repository that uses x-harness. ## What x-harness is x-harness is a Go-native, file-first admission and readiness harness for AI coding workflows. - It does **not** run agents. - It does **not** replace CI. - It does **not** guarantee that code is correct. It evaluates whether a completion claim is admissible under repository policy and emits one of two decisions: **accepted** or **withheld**. ## When to create or update completion-card.yaml Create or update `completion-card.yaml` at the root of the workspace when you finish a task and are ready to propose completion. Do this **before** claiming the task is done. The card must be written as YAML and must validate against the repository schema at `schemas/completion-card.schema.json`. ## How to record evidence Evidence must be explicit and reproducible. 1. **Files changed**: list every file you created or modified. 2. **Command evidence**: record the exact commands you ran, their exit codes, and when they ran. 3. **Manual rationale**: only use this when no command evidence is possible (light tier). 4. **State**: for standard and deep tiers, declare `read_set` and `write_set`. Do not include: - hidden network installations - commands that auto-enable external services - destructive commands without rollback context ## How to run verify / check Run the local verify gate before proposing completion: ```bash ./x-