Preview 0.33

P05: Turn a review finding into a tested repair

Know before you begin

A review finding becomes useful when you can reproduce it, fix it, and show what changed. Workshop Queue can store a blocked ticket, but its summary omits that ticket from the unresolved count. Follow that finding through a regression and repair.

Complete P04 and start from clean main in the same clone. Use your native terminal for Academy and Git, and the selected harness for agent requests.

Confirm the safe practice space

You · Browser · All operating systems

P05 is a Practitioner lab. Complete P04 in your own fork and Academy clone first. If you have not yet forked, cloned, installed Academy, and practiced the terminal boundary, return to F01 before continuing. P05 changes only the prepared Workshop Queue exercise, never the Academy source clone.

Why

A known fork and clone keep the remediation attempt separate from the course source and give Academy a repository it can reset safely.

Reviewed resources for Confirm the safe practice space

Expected result

You have a clean Academy learner clone, an installed Academy CLI from F01, and a codeArbiter harness pointed at that clone.

If that does not happen

If you are unsure which repository is your fork or where Academy is installed, stop and repeat F01. Do not run P05 in an unfamiliar checkout.

Evidence

This is a prerequisite check by you. Academy Check does not authenticate how you created the fork or clone.

What you will prove

Preserve three commits after Prepare: the checkpoint report and finding; the passing test and minimal repair together; then a schema-3 receipt naming the finding and repair commits. Observe RED before production changes and GREEN afterward. Do not commit a failing regression or claim that a receipt authenticates command chronology.

Prepare safely

Prepare the numbered remediation attempt

From the clean main branch at your Academy learner clone root, run Prepare in a native terminal. This command is entered directly in the terminal, so it never begins with !.

Why

Prepare creates the verifier-owned attempt branch and stages the real blocked-ticket summary defect before any learner work begins.

You · Native terminal · Windows

$academy = "$env:LOCALAPPDATA\ArbiterAcademy\preview-0.33\Scripts\arbiter-academy.exe"
& $academy --repository (Get-Location).Path prepare P05-checkpoint-remediation

You · Native terminal · macOS

academy="${XDG_DATA_HOME:-$HOME/.local/share}/arbiter-academy/preview-0.33/bin/arbiter-academy"
"$academy" --repository "$PWD" prepare P05-checkpoint-remediation

You · Native terminal · Linux

academy="${XDG_DATA_HOME:-$HOME/.local/share}/arbiter-academy/preview-0.33/bin/arbiter-academy"
"$academy" --repository "$PWD" prepare P05-checkpoint-remediation

Expected result

Academy prints academy/P05-checkpoint-remediation/ATTEMPT_NUMBER and prepares a blocked ticket whose summary count is intentionally wrong.

If that does not happen

Preserve the exact error. Resolve only the named clean-worktree or branch condition; do not force-reset main or delete an earlier attempt.

Evidence

The printed attempt branch and prepared commit are the baseline that Check later reconstructs.

Verify the prepared branch before changing anything

In the same native terminal, inspect the prepared branch, commit, and worktree. Compare the branch with the value Prepare printed. These are terminal commands, not harness commands, so do not add !.

Why

The three required commits count only when they descend from the prepared attempt, not from a look-alike local branch.

You · Native terminal · Windows

git branch --show-current
git rev-parse HEAD
git status --short

You · Native terminal · macOS

git branch --show-current
git rev-parse HEAD
git status --short

You · Native terminal · Linux

git branch --show-current
git rev-parse HEAD
git status --short

Expected result

The branch begins academy/P05-checkpoint-remediation/, HEAD is the prepared commit, and status prints no changed paths.

If that does not happen

If any value differs, preserve the output and use Reset. Do not rename a branch, rewrite history, or manually copy prepared files.

Evidence

You confirmed the attempt identity before creating the finding, green repair, and receipt commits.

Ask the agent to read the prepared boundary

In your active codeArbiter harness, send the copied message. This is a request to the agent, not a shell command, so it never begins with !. The agent reads; it must not edit or commit in this step.

Why

The learner and agent need the domain, persistence, reporting, decision, and scenario boundaries before deciding what the finding proves.

Your agent · Claude Code harness · All operating systems

Open .codearbiter/decisions/0005-terminal-blocked-ticket-lifecycle.md, .codearbiter/decisions/decision-log.md, training_scenarios/P05-checkpoint-remediation.json, tests/test_cli.py, workshop_queue/model.py, workshop_queue/service.py, and workshop_queue/cli.py. Show the prepared blocked-ticket behavior and the summary expression that omits it. Do not edit, stage, run a host command, or commit.

Your agent · Codex harness · All operating systems

Open .codearbiter/decisions/0005-terminal-blocked-ticket-lifecycle.md, .codearbiter/decisions/decision-log.md, training_scenarios/P05-checkpoint-remediation.json, tests/test_cli.py, workshop_queue/model.py, workshop_queue/service.py, and workshop_queue/cli.py. Show the prepared blocked-ticket behavior and the summary expression that omits it. Do not edit, stage, run a host command, or commit.

Your agent · Pi harness · All operating systems

Open .codearbiter/decisions/0005-terminal-blocked-ticket-lifecycle.md, .codearbiter/decisions/decision-log.md, training_scenarios/P05-checkpoint-remediation.json, tests/test_cli.py, workshop_queue/model.py, workshop_queue/service.py, and workshop_queue/cli.py. Show the prepared blocked-ticket behavior and the summary expression that omits it. Do not edit, stage, run a host command, or commit.

Expected result

The agent can identify that blocked tickets persist through the normal model and store, while the report's unresolved total counts only open and claimed tickets.

If that does not happen

If a required file is missing or the branch is not the prepared attempt, stop. Preserve the attempt and Reset instead of substituting a similar source file.

Evidence

This read establishes the repository boundary for your own inspection; it is not a verifier-authenticated review.

Prepare supplies the fictional ADR-0005 and its log entry for blocked-ticket behavior. Preserve them. P06 practices a separate source-backed context refresh.

Practice

Ask codeArbiter to surface the checkpoint finding

In the selected harness, send the host-native checkpoint command. This is a codeArbiter command, not a shell command, so it never begins with !.

Why

The checkpoint lane frames the observed product defect before the repair lane begins.

Your agent · Claude Code harness · All operating systems

/ca:checkpoint

Your agent · Codex harness · All operating systems

$ca-checkpoint

Your agent · Pi harness · All operating systems

/ca-checkpoint

Your agent · Pi harness · All operating systems

/skill:ca-checkpoint

Expected result

The agent reports that the blocked Workshop Queue ticket is omitted from the unresolved summary and names the report/test boundary.

If that does not happen

If the checkpoint reports another problem or cannot run, preserve its output and correct the named prerequisite or use Reset. Do not invent a checkpoint transcript.

Evidence

The finding commit below, not a chat transcript, is the repository artifact Check can inspect.

Inspect the real defect before recording it

You · Active codeArbiter harness · All operating systems

Read the checkpoint result next to the prepared summary boundary. Confirm the claim is narrow: RQ-105 is blocked, its reason is venue-access clearance, and the unresolved count excludes it. Do not ask the agent to repair the code yet.

Why

A precise finding prevents a generic report or unrelated product change from masquerading as remediation.

Expected result

You can state the observed defect in one sentence and identify tests/test_cli.py plus workshop_queue/cli.py as the later test and code boundaries.

If that does not happen

If the result is not the prepared blocked-ticket defect, stop and Reset. Do not broaden the exercise to make a different finding fit.

Evidence

This is your inspection. Check does not authenticate a checkpoint run or a person's review.

Ask the agent to record only the finding

After the selected checkpoint command writes its generated checkpoint report and .codearbiter/last-checkpoint, send this message in the selected harness. It asks the agent to make the first of three commits, carrying those real generated artifacts with the finding, and forbids the test or production repair in that commit.

Why

The verifier requires an exact, standalone finding commit before the RED regression and GREEN repair.

Your agent · Claude Code harness · All operating systems

Create .codearbiter/reports/academy/P05-finding.md with exactly these UTF-8 bytes, including the final newline:
# P05 Finding: blocked tickets omitted from unresolved summary

Ticket `RQ-105` is blocked: `Venue access is awaiting facilities clearance`.
Affected paths: `tests/test_cli.py`, `workshop_queue/cli.py`.

Then identify the one dated .codearbiter/checkpoints/YYYY-MM-DD.md generated by the just-run checkpoint and confirm .codearbiter/last-checkpoint exists. Stage exactly that generated report, .codearbiter/last-checkpoint, and .codearbiter/reports/academy/P05-finding.md; show the staged path list and diff, then invoke the CodeArbiter commit gate. Do not edit tests or production code, create the receipt, amend, or rebase.

Your agent · Codex harness · All operating systems

Create .codearbiter/reports/academy/P05-finding.md with exactly these UTF-8 bytes, including the final newline:
# P05 Finding: blocked tickets omitted from unresolved summary

Ticket `RQ-105` is blocked: `Venue access is awaiting facilities clearance`.
Affected paths: `tests/test_cli.py`, `workshop_queue/cli.py`.

Then identify the one dated .codearbiter/checkpoints/YYYY-MM-DD.md generated by the just-run checkpoint and confirm .codearbiter/last-checkpoint exists. Stage exactly that generated report, .codearbiter/last-checkpoint, and .codearbiter/reports/academy/P05-finding.md; show the staged path list and diff, then invoke the CodeArbiter commit gate. Do not edit tests or production code, create the receipt, amend, or rebase.

Your agent · Pi harness · All operating systems

Create .codearbiter/reports/academy/P05-finding.md with exactly these UTF-8 bytes, including the final newline:
# P05 Finding: blocked tickets omitted from unresolved summary

Ticket `RQ-105` is blocked: `Venue access is awaiting facilities clearance`.
Affected paths: `tests/test_cli.py`, `workshop_queue/cli.py`.

Then identify the one dated .codearbiter/checkpoints/YYYY-MM-DD.md generated by the just-run checkpoint and confirm .codearbiter/last-checkpoint exists. Stage exactly that generated report, .codearbiter/last-checkpoint, and .codearbiter/reports/academy/P05-finding.md; show the staged path list and diff, then invoke the CodeArbiter commit gate. Do not edit tests or production code, create the receipt, amend, or rebase.

Expected result

One new descendant commit changes the generated dated checkpoint report, .codearbiter/last-checkpoint, and .codearbiter/reports/academy/P05-finding.md; it changes no test or production path.

If that does not happen

If a generated checkpoint artifact is absent, another path is staged, or the finding content differs, stop before committing. Preserve the attempt and Reset rather than amending a malformed evidence history.

Evidence

The first descendant commit preserves the real checkpoint side effects and proves the finding was recorded before the regression and repair.

Verify the finding commit boundary

Use a native terminal to inspect only the latest commit path list. These are direct terminal commands and never begin with !.

Why

A clean three-artifact commit gives the later history an unambiguous checkpoint-and-finding boundary.

You · Native terminal · Windows

git log -1 --format=%H
git diff-tree --no-commit-id --name-only -r HEAD

You · Native terminal · macOS

git log -1 --format=%H
git diff-tree --no-commit-id --name-only -r HEAD

You · Native terminal · Linux

git log -1 --format=%H
git diff-tree --no-commit-id --name-only -r HEAD

Expected result

The path list contains the generated dated checkpoint report, .codearbiter/last-checkpoint, and .codearbiter/reports/academy/P05-finding.md only.

If that does not happen

If the commit omits either checkpoint artifact or contains another path, preserve the attempt and Reset. Do not rewrite the commit with amend or rebase.

Evidence

The commit ID is later written into the final receipt as finding_commit.

Explain the defect before requesting code: RQ-105 is blocked, so it is unresolved, but the current expression counts only open and claimed tickets.

Ask the agent to add the test-only RED regression

Send this message in the selected harness. The agent must change only the test, run it, and stop at the meaningful failing assertion before any production edit.

Why

The lesson proves that the prepared report is wrong with a real persisted blocked ticket rather than a synthetic JSON assertion.

Your agent · Claude Code harness · All operating systems

Change only tests/test_cli.py. The verifier does not accept an equivalent test. Insert this exact method in WorkshopQueueCliTests:
    def test_report_json_counts_blocked_ticket_as_unresolved(self) -> None:
        tickets = json.loads(self.fixture.read_text(encoding="utf-8"))
        tickets[0]["id"] = "RQ-105"
        self.fixture.write_text(json.dumps(tickets), encoding="utf-8")
        claim_result = self.run_cli("claim", "RQ-105", "--volunteer", "Sam")
        block_result = self.run_cli("block", "RQ-105", "--reason", "Venue access is awaiting facilities clearance")
        report = self.run_cli("report", "--format", "json")
        self.assertEqual(claim_result.returncode, 0, claim_result.stderr)
        self.assertEqual(block_result.returncode, 0, block_result.stderr)
        self.assertEqual(report.returncode, 0, report.stderr)
        parsed = json.loads(report.stdout)
        self.assertEqual(parsed["blocked"], 1)
        self.assertEqual(parsed["unresolved"], 1)
Run only the exact focused test with python -m unittest tests.test_cli.WorkshopQueueCliTests.test_report_json_counts_blocked_ticket_as_unresolved -v and stop when it fails because unresolved is 0 instead of 1. Do not edit workshop_queue, stage, or commit yet.

Your agent · Codex harness · All operating systems

Change only tests/test_cli.py. The verifier does not accept an equivalent test. Insert this exact method in WorkshopQueueCliTests:
    def test_report_json_counts_blocked_ticket_as_unresolved(self) -> None:
        tickets = json.loads(self.fixture.read_text(encoding="utf-8"))
        tickets[0]["id"] = "RQ-105"
        self.fixture.write_text(json.dumps(tickets), encoding="utf-8")
        claim_result = self.run_cli("claim", "RQ-105", "--volunteer", "Sam")
        block_result = self.run_cli("block", "RQ-105", "--reason", "Venue access is awaiting facilities clearance")
        report = self.run_cli("report", "--format", "json")
        self.assertEqual(claim_result.returncode, 0, claim_result.stderr)
        self.assertEqual(block_result.returncode, 0, block_result.stderr)
        self.assertEqual(report.returncode, 0, report.stderr)
        parsed = json.loads(report.stdout)
        self.assertEqual(parsed["blocked"], 1)
        self.assertEqual(parsed["unresolved"], 1)
Run only the exact focused test with python -m unittest tests.test_cli.WorkshopQueueCliTests.test_report_json_counts_blocked_ticket_as_unresolved -v and stop when it fails because unresolved is 0 instead of 1. Do not edit workshop_queue, stage, or commit yet.

Your agent · Pi harness · All operating systems

Change only tests/test_cli.py. The verifier does not accept an equivalent test. Insert this exact method in WorkshopQueueCliTests:
    def test_report_json_counts_blocked_ticket_as_unresolved(self) -> None:
        tickets = json.loads(self.fixture.read_text(encoding="utf-8"))
        tickets[0]["id"] = "RQ-105"
        self.fixture.write_text(json.dumps(tickets), encoding="utf-8")
        claim_result = self.run_cli("claim", "RQ-105", "--volunteer", "Sam")
        block_result = self.run_cli("block", "RQ-105", "--reason", "Venue access is awaiting facilities clearance")
        report = self.run_cli("report", "--format", "json")
        self.assertEqual(claim_result.returncode, 0, claim_result.stderr)
        self.assertEqual(block_result.returncode, 0, block_result.stderr)
        self.assertEqual(report.returncode, 0, report.stderr)
        parsed = json.loads(report.stdout)
        self.assertEqual(parsed["blocked"], 1)
        self.assertEqual(parsed["unresolved"], 1)
Run only the exact focused test with python -m unittest tests.test_cli.WorkshopQueueCliTests.test_report_json_counts_blocked_ticket_as_unresolved -v and stop when it fails because unresolved is 0 instead of 1. Do not edit workshop_queue, stage, or commit yet.

Expected result

Only tests/test_cli.py changes, and the focused test fails because the report says unresolved is 0 when the persisted blocked ticket makes it 1.

If that does not happen

If the test fails for an import, file, fixture, or command error, fix neither production nor unrelated setup. Preserve the output and Reset for a new attempt.

Evidence

The final green repair contains this regression and the bounded implementation. Check does not establish when the test was run.

Recognize the meaningful RED result

You · Active codeArbiter harness · All operating systems

Read the focused test result. The important failure is the unresolved assertion after a successful claim, block, and report, not a syntax, import, fixture, or command failure.

Why

A failing test demonstrates the product defect before the repair changes the report expression.

Expected result

The focused test reaches the JSON report and shows that blocked is 1 while unresolved is still counted incorrectly.

If that does not happen

If the test did not reach the unresolved assertion, do not continue to GREEN. Preserve the attempt and Reset instead of repairing a different problem.

Evidence

You observe this runtime result during the lesson. Final Check validates the committed test and repair, not command chronology.

Keep the test uncommitted. Successful claim, block, and report commands followed by the wrong unresolved count are the meaningful RED result.

Repair the unresolved count

After observing RED, request the minimal repair. Keep the uncommitted regression unchanged.

Why

The bounded repair changes the definition of unresolved from open plus claimed to every ticket that is not completed.

Your agent · Claude Code harness · All operating systems

Change only workshop_queue/cli.py so the unresolved total is sum(ticket.status is not TicketStatus.COMPLETED for ticket in tickets). Do not change tests. Run the exact focused blocked-ticket test and stop after it passes. Do not stage or commit yet.

Your agent · Codex harness · All operating systems

Change only workshop_queue/cli.py so the unresolved total is sum(ticket.status is not TicketStatus.COMPLETED for ticket in tickets). Do not change tests. Run the exact focused blocked-ticket test and stop after it passes. Do not stage or commit yet.

Your agent · Pi harness · All operating systems

Change only workshop_queue/cli.py so the unresolved total is sum(ticket.status is not TicketStatus.COMPLETED for ticket in tickets). Do not change tests. Run the exact focused blocked-ticket test and stop after it passes. Do not stage or commit yet.

Expected result

The focused blocked-ticket test passes.

If that does not happen

If the focused test remains red or another production path changes, stop. Preserve the result and Reset rather than broadening the repair.

Evidence

An actual GREEN result follows the observed RED result.

Commit the green regression and repair

After the focused test and affected CLI suite pass, commit the test and repair together, with this repair's queued fix work item if codeArbiter recorded one.

Why

A green commit keeps the regression and implementation together after verification.

Your agent · Claude Code harness · All operating systems

Run the focused blocked-ticket regression and tests.test_cli. If both pass, stage only tests/test_cli.py and workshop_queue/cli.py, plus .codearbiter/open-tasks.md only when its sole change is this repair's queued fix work item, show the staged diff, and invoke the codeArbiter commit gate. Leave any such item queued. Keep the regression unchanged since RED. Do not create the receipt, amend, or rebase.

Your agent · Codex harness · All operating systems

Run the focused blocked-ticket regression and tests.test_cli. If both pass, stage only tests/test_cli.py and workshop_queue/cli.py, plus .codearbiter/open-tasks.md only when its sole change is this repair's queued fix work item, show the staged diff, and invoke the codeArbiter commit gate. Leave any such item queued. Keep the regression unchanged since RED. Do not create the receipt, amend, or rebase.

Your agent · Pi harness · All operating systems

Run the focused blocked-ticket regression and tests.test_cli. If both pass, stage only tests/test_cli.py and workshop_queue/cli.py, plus .codearbiter/open-tasks.md only when its sole change is this repair's queued fix work item, show the staged diff, and invoke the codeArbiter commit gate. Leave any such item queued. Keep the regression unchanged since RED. Do not create the receipt, amend, or rebase.

Expected result

One green commit changes tests/test_cli.py and workshop_queue/cli.py, plus at most one queued fix work item on .codearbiter/open-tasks.md.

If that does not happen

Before committing, confirm that both the regression test and repair are staged. If either is missing or unrelated paths are staged, correct the staged selection and review it again. Do not amend or rebase the attempt history.

Evidence

RED remains an observed result, not a failing commit.

From codeArbiter 3.8, the fix lane records an authorized repair as one fix work item. On this practice board that is one queued row. Stage it with the repair so the commit gate reviews it in the green commit, and leave it queued.

Generate the exact receipt bytes last

Run the complete command for your operating system in the native terminal only after the finding and green repair commits exist. It reads the two real commit IDs from Git, writes deterministic verifier-owned bytes, stages only the receipt, and shows the staged diff. Do not hand-edit the JSON.

Why

The fixed generator sorts keys, uses compact separators and ASCII escaping, and appends exactly one LF so the final receipt matches Check byte for byte.

You · Native terminal · Windows

@'
import json
import pathlib
import subprocess

def git(*arguments):
    return subprocess.run(["git", *arguments], check=True, stdout=subprocess.PIPE, text=True).stdout

if git("status", "--porcelain", "--untracked-files=all"):
    raise SystemExit("P05 receipt requires a clean worktree after GREEN")
reference_oid = git("rev-parse", "HEAD").strip()
commits = git("rev-list", "--reverse", "HEAD~2..HEAD").splitlines()
hex_digits = "0123456789abcdef"
if (
    not reference_oid
    or any(character not in hex_digits for character in reference_oid)
    or len(commits) != 2
    or any(
        len(commit) != len(reference_oid)
        or any(character not in hex_digits for character in commit)
        for commit in commits
    )
):
    raise SystemExit("P05 receipt requires exactly two commit IDs after Prepare")
payload = {
    "affected_paths": ["tests/test_cli.py", "workshop_queue/cli.py"],
    "finding_commit": commits[0],
    "finding_id": "ACADEMY-P05-BLOCKED-UNRESOLVED",
    "remediation_commit": commits[1],
    "schema_version": 3,
    "status": "remediated",
}
receipt = pathlib.Path(".codearbiter/checkpoints/P05-academy.json")
receipt.parent.mkdir(parents=True, exist_ok=True)
receipt.write_bytes(json.dumps(payload, sort_keys=True, separators=(",", ":"), ensure_ascii=True).encode("utf-8") + b"\n")
subprocess.run(["git", "add", "--", receipt.as_posix()], check=True)
subprocess.run(["git", "diff", "--cached", "--", receipt.as_posix()], check=True)
'@ | python -

You · Native terminal · macOS

python3 - <<'PY'
import json
import pathlib
import subprocess

def git(*arguments):
    return subprocess.run(["git", *arguments], check=True, stdout=subprocess.PIPE, text=True).stdout

if git("status", "--porcelain", "--untracked-files=all"):
    raise SystemExit("P05 receipt requires a clean worktree after GREEN")
reference_oid = git("rev-parse", "HEAD").strip()
commits = git("rev-list", "--reverse", "HEAD~2..HEAD").splitlines()
hex_digits = "0123456789abcdef"
if (
    not reference_oid
    or any(character not in hex_digits for character in reference_oid)
    or len(commits) != 2
    or any(
        len(commit) != len(reference_oid)
        or any(character not in hex_digits for character in commit)
        for commit in commits
    )
):
    raise SystemExit("P05 receipt requires exactly two commit IDs after Prepare")
payload = {
    "affected_paths": ["tests/test_cli.py", "workshop_queue/cli.py"],
    "finding_commit": commits[0],
    "finding_id": "ACADEMY-P05-BLOCKED-UNRESOLVED",
    "remediation_commit": commits[1],
    "schema_version": 3,
    "status": "remediated",
}
receipt = pathlib.Path(".codearbiter/checkpoints/P05-academy.json")
receipt.parent.mkdir(parents=True, exist_ok=True)
receipt.write_bytes(json.dumps(payload, sort_keys=True, separators=(",", ":"), ensure_ascii=True).encode("utf-8") + b"\n")
subprocess.run(["git", "add", "--", receipt.as_posix()], check=True)
subprocess.run(["git", "diff", "--cached", "--", receipt.as_posix()], check=True)
PY

You · Native terminal · Linux

python3 - <<'PY'
import json
import pathlib
import subprocess

def git(*arguments):
    return subprocess.run(["git", *arguments], check=True, stdout=subprocess.PIPE, text=True).stdout

if git("status", "--porcelain", "--untracked-files=all"):
    raise SystemExit("P05 receipt requires a clean worktree after GREEN")
reference_oid = git("rev-parse", "HEAD").strip()
commits = git("rev-list", "--reverse", "HEAD~2..HEAD").splitlines()
hex_digits = "0123456789abcdef"
if (
    not reference_oid
    or any(character not in hex_digits for character in reference_oid)
    or len(commits) != 2
    or any(
        len(commit) != len(reference_oid)
        or any(character not in hex_digits for character in commit)
        for commit in commits
    )
):
    raise SystemExit("P05 receipt requires exactly two commit IDs after Prepare")
payload = {
    "affected_paths": ["tests/test_cli.py", "workshop_queue/cli.py"],
    "finding_commit": commits[0],
    "finding_id": "ACADEMY-P05-BLOCKED-UNRESOLVED",
    "remediation_commit": commits[1],
    "schema_version": 3,
    "status": "remediated",
}
receipt = pathlib.Path(".codearbiter/checkpoints/P05-academy.json")
receipt.parent.mkdir(parents=True, exist_ok=True)
receipt.write_bytes(json.dumps(payload, sort_keys=True, separators=(",", ":"), ensure_ascii=True).encode("utf-8") + b"\n")
subprocess.run(["git", "add", "--", receipt.as_posix()], check=True)
subprocess.run(["git", "diff", "--cached", "--", receipt.as_posix()], check=True)
PY

Expected result

The command shows only .codearbiter/checkpoints/P05-academy.json staged; its compact sorted-key JSON names the real finding and green repair commit IDs and ends in exactly one LF.

If that does not happen

If generation stops, an ID is missing, a path is extra, or GREEN is not clean, do not hand-write JSON or rewrite history. Preserve the attempt and Reset.

Evidence

A schema-3 receipt binds the finding and green repair commits without claiming a RED commit.

Ask the agent to commit the final receipt

Send this message in the selected harness after reviewing the staged receipt.

Why

The receipt must be last so it can bind the already-committed finding and green repair evidence.

Your agent · Claude Code harness · All operating systems

Confirm the staged path list is exactly .codearbiter/checkpoints/P05-academy.json, then invoke the CodeArbiter commit gate. Do not add files, amend, rebase, or push.

Your agent · Codex harness · All operating systems

Confirm the staged path list is exactly .codearbiter/checkpoints/P05-academy.json, then invoke the CodeArbiter commit gate. Do not add files, amend, rebase, or push.

Your agent · Pi harness · All operating systems

Confirm the staged path list is exactly .codearbiter/checkpoints/P05-academy.json, then invoke the CodeArbiter commit gate. Do not add files, amend, rebase, or push.

Expected result

The third and final descendant commit changes exactly .codearbiter/checkpoints/P05-academy.json.

If that does not happen

If the commit gate reports a boundary problem, preserve the attempt and use Reset. Never force a receipt into an earlier commit.

Evidence

The committed receipt is the only P05 artifact Academy Check reads as the final evidence binding.

Recognize success

The first commit contains the generated dated checkpoint report, .codearbiter/last-checkpoint, and .codearbiter/reports/academy/P05-finding.md. The second contains tests/test_cli.py and workshop_queue/cli.py. The third contains only .codearbiter/checkpoints/P05-academy.json.

The unchanged regression reaches the real CLI. The repair counts every ticket that is not completed. The schema-3 receipt names finding_commit and remediation_commit; it has no red_commit field.

Confirm the completed attempt is clean

Before Check, inspect the worktree in a native terminal. This is a direct terminal command and never begins with !.

Why

P05 Check rejects uncommitted or unrelated state so the three commits record the finding, verified repair, and receipt.

You · Native terminal · Windows

git status --short --untracked-files=all

You · Native terminal · macOS

git status --short --untracked-files=all

You · Native terminal · Linux

git status --short --untracked-files=all

Expected result

Git prints no changed or untracked paths.

If that does not happen

If status is not empty, do not delete evidence or add unrelated files to a P05 commit. Preserve the attempt and Reset.

Evidence

A clean worktree is a direct Check precondition.

Check

Run the external Academy Check

Run Check from the Academy learner clone root in a native terminal. This command is entered directly and never begins with !.

Why

Check independently reconstructs the prepared fixture, commit ancestry, exact path roles, regression, repair, receipt, and live worktree.

You · Native terminal · Windows

$academy = "$env:LOCALAPPDATA\ArbiterAcademy\preview-0.33\Scripts\arbiter-academy.exe"
& $academy --repository (Get-Location).Path check P05-checkpoint-remediation

You · Native terminal · macOS

academy="${XDG_DATA_HOME:-$HOME/.local/share}/arbiter-academy/preview-0.33/bin/arbiter-academy"
"$academy" --repository "$PWD" check P05-checkpoint-remediation

You · Native terminal · Linux

academy="${XDG_DATA_HOME:-$HOME/.local/share}/arbiter-academy/preview-0.33/bin/arbiter-academy"
"$academy" --repository "$PWD" check P05-checkpoint-remediation

Expected result

Check prints checkpoint P05-checkpoint-remediation: passed and records progress in .academy/progress.json.

If that does not happen

If Check fails, preserve the committed attempt and read the failed predicate. Start a new numbered attempt with Reset instead of rewriting committed evidence.

Evidence

Check validates Git artifacts and the final worktree. It does not authenticate a checkpoint run or a human review, and it does not prove command chronology.

Check validates the prepared fixture, finding, source changes, three-commit history, receipt, and clean worktree. It cannot authenticate a checkpoint invocation, a human review, or RED/GREEN chronology. Keep those actual observations separate.

Recover or continue

Create a preserved numbered retry

Use Reset only when P05 needs another attempt. Run it at the Academy learner clone root in a native terminal; the command never begins with !.

Why

Reset preserves the failed or incomplete attempt for inspection before creating the next numbered baseline.

You · Native terminal · Windows

$academy = "$env:LOCALAPPDATA\ArbiterAcademy\preview-0.33\Scripts\arbiter-academy.exe"
& $academy --repository (Get-Location).Path reset P05-checkpoint-remediation

You · Native terminal · macOS

academy="${XDG_DATA_HOME:-$HOME/.local/share}/arbiter-academy/preview-0.33/bin/arbiter-academy"
"$academy" --repository "$PWD" reset P05-checkpoint-remediation

You · Native terminal · Linux

academy="${XDG_DATA_HOME:-$HOME/.local/share}/arbiter-academy/preview-0.33/bin/arbiter-academy"
"$academy" --repository "$PWD" reset P05-checkpoint-remediation

Expected result

Academy preserves the earlier attempt and prints the next academy/P05-checkpoint-remediation/ATTEMPT_NUMBER branch.

If that does not happen

If Reset stops, preserve its message and resolve only the named repository condition. Never force-reset or delete a prior attempt.

Evidence

A new attempt begins from the clean fixture while the previous history remains inspectable.

Hint 1. Inspect each commit's paths. Keep finding, repair, and receipt separate.

Hint 2. A setup error is not evidence of the summary bug. Confirm the CLI commands succeeded before reading the count assertion.

Hint 3. Generate the receipt last. Never guess an ID or invent a RED commit.

Leave the completed attempt intact and return to clean main before P06.

Understand the mechanism

A checkpoint can surface many findings. Take one through a complete repair and keep adjacent cleanup separate. The receipt connects a diagnosis to its result and does not replace tests. Test-First Evidence and Checkpoints explain the evidence and the review.

Use this in your own project. Ask for a finding's impact and reproduction, repair the affected behavior, and report what remains open.

Next step

Continue with P06-context-drift-recovery.

Recovery guidance