chore(release): prepare @aictrl/cli 0.4.6

[byapparov]

Version bump for the 0.4.6 release, following RELEASING.md.

• packages/cli/package.json and the packages/cli workspace entry in bun.lock go to 0.4.6. bun install --frozen-lockfile passes.
• RELEASING.md: the 0.4.6 candidate notes replace the 0.4.5 section.
• The RELEASING.md release regressions, plus test/cli/run-output-schema.test.ts: 124 pass, 0 fail.

What 0.4.6 ships (merged in #129): aictrl run --output-schema with bounded corrective retries and --output-result (exit 2 for configuration errors, exit 3 for structured-output failures), the --attach request-shape fix, and the models.dev body-timeout fix.

After merge: gh release create v0.4.6 --target <merge SHA>, then the publish workflow and an install check.

🤖 Generated with Claude Code

[aictrl-dev]

🟠 0.4.6 regressions missing from release test gate.

🤖 Fix with your agent

Fix this code review finding (aictrl-dev/cli PR #133, RELEASING.md:39-52):

Problem: 0.4.6 regressions missing from release test gate
Detail: The candidate section is bumped to 0.4.6, whose headline feature is structured output (#129), but the release-regression `bun test` list in step 2 of this document still contains only the 0.4.5-era suite and was not extended in this PR. Dedicated regressions for the new feature exist (packages/cli/test/session/structured-output.test.ts, packages/cli/test/session/structured-output-integration.test.ts, packages/cli/test/cli/run-schema-v1.test.ts), so the documented pre-release gate no longer covers the current candidate's features, breaking the file's own convention that the regression list tracks the candidate.
Suggested fix: Extend the step 2 regression `bun test` list with the structured-output suites, e.g. add `packages/cli/test/cli/run-schema-v1.test.ts packages/cli/test/session/structured-output.test.ts packages/cli/test/session/structured-output-integration.test.ts` (plus any `run-output-schema` regression if present on the branch) to the documented pre-release command.

Implement the fix on the PR head branch and add a regression test that fails before the fix and passes after.

Why this matters

The candidate section is bumped to 0.4.6, whose headline feature is structured output (#129), but the release-regression bun test list in step 2 of this document still contains only the 0.4.5-era suite and was not extended in this PR. Dedicated regressions for the new feature exist (packages/cli/test/session/structured-output.test.ts, packages/cli/test/session/structured-output-integration.test.ts, packages/cli/test/cli/run-schema-v1.test.ts), so the documented pre-release gate no longer covers the current candidate's features, breaking the file's own convention that the regression list tracks the candidate.

## 0.4.6 candidate

- `aictrl run --output-schema <file>` enforces a JSON Schema on the final
  result with bounded corrective retries (`--output-schema-retries`, default 2)
  and writes only the validated value to `--output-result <file>` (#129).
  Exit 2 is a schema configuration error; exit 3 is a structured-output failure.
  New NDJSON events `structured_output_rejected` and a terminal
  `structured_output` are additive (schema "1"). Runs without a schema are
  unchanged.

[aictrl-dev]

⚪ Issue refs drop 'CLI' prefix used in prior section.

Suggested change

	and writes only the validated value to `--output-result <file>` (#129).
	Write "(CLI #129)" on the three new references to match the previous section's style, or normalize the whole file to one style.

🤖 Fix with your agent

Fix this code review finding (aictrl-dev/cli PR #133, RELEASING.md:43):

Problem: Issue refs drop 'CLI' prefix used in prior section
Detail: The replaced section used "CLI #127" / "CLI #126" for issue references, while the new 0.4.6 section uses bare "(#129)" three times yet keeps the "application #5960" prefix style. The mixed reference style deviates from the file's own prior convention for first mentions.
Suggested fix: Write "(CLI #129)" on the three new references to match the previous section's style, or normalize the whole file to one style.

Implement the fix on the PR head branch and add a regression test that fails before the fix and passes after.

Why this matters

The replaced section used "CLI #127" / "CLI #126" for issue references, while the new 0.4.6 section uses bare "(#129)" three times yet keeps the "application #5960" prefix style. The mixed reference style deviates from the file's own prior convention for first mentions.

[aictrl-dev]

Code review

Verdict: Address the major findings before merging. · 🔴 0 · 🟠 1 · 🟡 0 · ⚪ 1 · 0/2 resolved

• 🟠 RELEASING.md:39-52 — 0.4.6 regressions missing from release test gate
• ⚪ RELEASING.md:43 — Issue refs drop 'CLI' prefix used in prior section

🤖 Fix all 2 open findings with your agent

Fix the following code review findings on aictrl-dev/cli PR #133 (head branch).
Run the relevant tests/linters after each change.

1. RELEASING.md:39-52 — 0.4.6 regressions missing from release test gate
   Detail: The candidate section is bumped to 0.4.6, whose headline feature is structured output (#129), but the release-regression `bun test` list in step 2 of this document still contains only the 0.4.5-era suite and was not extended in this PR. Dedicated regressions for the new feature exist (packages/cli/test/session/structured-output.test.ts, packages/cli/test/session/structured-output-integration.test.ts, packages/cli/test/cli/run-schema-v1.test.ts), so the documented pre-release gate no longer covers the current candidate's features, breaking the file's own convention that the regression list tracks the candidate.
   Suggested fix: Extend the step 2 regression `bun test` list with the structured-output suites, e.g. add `packages/cli/test/cli/run-schema-v1.test.ts packages/cli/test/session/structured-output.test.ts packages/cli/test/session/structured-output-integration.test.ts` (plus any `run-output-schema` regression if present on the branch) to the documented pre-release command.
2. RELEASING.md:43 — Issue refs drop 'CLI' prefix used in prior section
   Detail: The replaced section used "CLI #127" / "CLI #126" for issue references, while the new 0.4.6 section uses bare "(#129)" three times yet keeps the "application #5960" prefix style. The mixed reference style deviates from the file's own prior convention for first mentions.
   Suggested fix: Write "(CLI #129)" on the three new references to match the previous section's style, or normalize the whole file to one style.

📋 Out-of-diff findings (2)

Sev	Location	Finding
🟠	RELEASING.md:39-52	0.4.6 regressions missing from release test gate
⚪	RELEASING.md:43	Issue refs drop 'CLI' prefix used in prior section

Reviewed 3 files · 0 inline · view all 2 findings ↗

---

aictrl · AI code review for fast-moving teams · aictrl.dev