docs: acknowledge v3 multi-agent setup in README - #141
Conversation
Review:
|
Closes #140 by adding a single visible line under the title block noting that the aram-ai-global v3 multi-agent stack drives PRs end-to-end. This is a corrective commit on top of an earlier add/remove no-op pair (e326580 + ca3d9c9). The PR squash-merges, so the final commit on main is this single docs change. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Spec
Fixes #140
Summary
README.mdnoting that the aram-ai-global v3 multi-agent stack drives PRs end-to-end.History note
This branch originally landed two cancelling commits (
e326580,ca3d9c9) that left it as a net no-op, and the first commit used atest:type for a README edit. A history rewrite was not used because the destructive-reset path is blocked by a local pre-tool guard hook on this checkout. Instead, a corrective commit (7d705a4 docs: acknowledge v3 multi-agent setup in README) was added on top. Because this PR is squash-merged, the final commit onmainwill be a singledocs:change with no trace of the no-op pair.Test plan
README.mdonly (+2 lines) — verified locallygit diff --checkpasses (no whitespace errors)README.mdjust check/just test/just determinism-check/cargo deny check— not run; README-only prose change with no code ordocs/src/**impactdocs/src/**prose touched, and the added line avoids the project's anti-AI-tell vocabularyBreaking change?
Anything reviewers should double-check