Preview 0.33

U07: Deliver a tested fix for review

Know before you begin

This capstone combines scope, regression testing, review, and a real pull request. Complete U06 first. Start from clean main in your fork, with the terminal and harness at that same clone.

The prepared defect accepts control characters in ticket resolutions. Use the fix lane for this known bug. It does not need a feature mini-spec or a small-lane record.

What you will prove

Reject newline, tab, and DEL while preserving ordinary resolution text. Observe the focused regression fail, make the minimal repair, then run affected service checks. Commit the passing test with its repair.

Open a real PR in your personal fork and retain its browser URL. The local Academy Check and the hosted pull request establish different facts.

Prepare safely

Return safely to the Academy base branch

After completing U06, use a native terminal at the Academy clone root to return to main and confirm the checkout is clean before preparing U07. This preserves the completed U06 attempt branch.

Why

U07 Prepare creates its own numbered branch from main; it must not start from a previous lesson attempt.

You · Native terminal · Windows

git switch main
git status --short

You · Native terminal · macOS

git switch main
git status --short

You · Native terminal · Linux

git switch main
git status --short

Expected result

HEAD is on main and git status --short prints nothing; the completed U06 attempt branch remains intact.

If that does not happen

If switching branches would overwrite or hide work, stop and preserve that work on its existing branch. Do not force-switch, reset, rebase, delete, or alter the earlier attempt. Next safe step: return only after the checkout is clean.

Evidence

The branch name and clean status establish the base-branch precondition for the U07 attempt.

Prepare the bounded fix attempt

From a clean main branch at the Academy clone root, run Prepare in a native terminal. Academy creates the numbered attempt branch and seeds one known control-character defect. Stay on that branch for the capstone.

Why

The fixture makes the implementation boundary inspectable without replacing codeArbiter's fix workflow.

You · Native terminal · Windows

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

You · Native terminal · macOS

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

You · Native terminal · Linux

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

Expected result

Academy prints academy/U07-capstone/ATTEMPT_NUMBER. The branch is clean and tests/test_service.py contains a passing case that shows the existing resolution behavior accepts a control character. The fix lane will add the missing resolution regression.

If that does not happen

If Prepare names a dirty-worktree, branch, or remote problem, preserve the message and repair only that condition. Do not force-reset main or borrow another lesson's history.

Evidence

Keep the printed attempt branch and verify that git status --short is empty before entering the fix lane.

Stay on the numbered branch. Read the existing resolution behavior. Do not add a made-up review, approval, feature classification, or PR record.

Practice

Repair the known defect through the fix lane

Use the fix command. Add the missing resolution regression, observe RED, make the minimal repair, and run affected service checks.

Why

The fix lane owns the regression, minimal repair, affected verification, and commit gate.

You · Claude Code harness · All operating systems

/ca:fix "Reject control characters in ticket resolutions"

You · Codex harness · All operating systems

$ca-fix "Reject control characters in ticket resolutions"

You · Pi harness · All operating systems

/ca-fix "Reject control characters in ticket resolutions"

You · Pi harness · All operating systems

/skill:ca-fix "Reject control characters in ticket resolutions"

Expected result

The regression and repair are ready for one green commit.

If that does not happen

If the proposed scope expands or the fix lane reports a stop, do not hand-write substitute artifacts. Preserve the branch and resolve the named real gate, or use Reset for a new attempt.

Evidence

Actual checks and committed source; no feature classification is required.

The test must reach complete_ticket and the service must still accept ordinary text. Read the failure and final diff. Reject unrelated dependency, storage, or API changes.

Open and inspect your fork pull request

You · Browser · All operating systems

Request the governed commit of the green fix, then choose Open a PR at the branch handoff. Confirm the base repository is your personal fork before creation. Leave the PR open; do not merge.

Why

The bounded fix ends through a real hosted PR. Academy must not imitate that event with a local file.

Expected result

A real open PR inside your fork with the intended base and head.

If that does not happen

If no PR opens, keep the clean branch and use the real delivery workflow's recovery. Do not write a local PR receipt or claim a review that did not happen.

Evidence

Retain the browser URL. Academy does not authenticate a hosted event.

Inspect the actual base repository and branch before creating the PR. A safe origin push does not guarantee that a hosting tool selected your fork as the PR base. Keep the exercise PR inside your fork and leave merge for a separate decision.

Recognize success

The branch is clean, the focused regression and narrow service repair are committed, and the affected checks passed. Your fork shows the correct open pull request.

Explain what the test protects and which checks ran. An open PR, local Check, passing CI, review approval, merge, and release are separate states.

Check

Check durable local evidence

Run Check after the committed fix is clean. It inspects the prepared baseline, test, service behavior, safe remotes, and worktree.

Why

Check independently verifies durable repository facts without claiming that a harness command, review, PR, CI run, or merge occurred.

You · Native terminal · Windows

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

You · Native terminal · macOS

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

You · Native terminal · Linux

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

Expected result

The local fix passes its bounded Check.

If that does not happen

Read the failed predicate and correct the real branch boundary it identifies. Do not create a PR, review, CI, or approval receipt to influence Check.

Evidence

Local evidence; hosted review and CI are separate.

Check validates the prepared baseline, bounded committed source, executable service behavior, safe remotes, and clean worktree. It cannot prove earlier RED chronology, a host invocation, a human approval, hosted CI, review, or merge.

Recover or continue

Preserve the branch before a retry

Use Reset only if this attempt cannot be repaired. Run it from the matching clean Academy attempt branch. Academy archives the current branch before creating a new numbered attempt.

Why

A preserved retry leaves the failed fix evidence inspectable and avoids rewriting history or deleting a real hosted branch.

You · Native terminal · Windows

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

You · Native terminal · macOS

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

You · Native terminal · Linux

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

Expected result

Academy preserves the old attempt on an academy/archive/U07-capstone timestamped branch and prints a clean next attempt branch.

If that does not happen

If Reset refuses, preserve its output and current branch. Resolve only the stated repository condition. Never force-reset, rebase, delete the old attempt, or close a real PR to make the retry easier.

Evidence

The archive branch and the new numbered branch remain reachable for separate inspection.

Hint 1. Reproduce the defect before editing the service. A final passing test alone does not show that it caught the bug.

Hint 2. Inspect the actual PR in the browser. A local URL field proves no hosted event.

Hint 3. Preserve a failed attempt. Correct real defects through the fix lane; use Reset when the attempt needs a fresh baseline.

Understand the mechanism

You have taken a concrete problem from reproduction to reviewable delivery. Build a Feature End to End covers the same lane.

Build something of your own. Choose a useful feature, such as filtering a reading list. State who uses it, one success case, one failure case, and what is out of scope. Ask codeArbiter to build it through the feature lane, with a review pause where it helps. Use the Home page's own-project guide for setup.

Next step

none is not available in Arbiter Academy Preview 0.33.

Recovery guidance