Commit d61df30
feat(auto): wire driver selection through capabilities (#672)
* Add selected driver and brake mode for auto interviews
* fix(auto): align selected driver resume state
* feat(auto): wire driver selection through capabilities
* fix(auto): prompt for interview driver selection
* fix(auto): only prompt installed interview drivers
* fix(auto): preserve driver scaffold ledger sources
* fix(auto): scope add-keyword brake gate to feature additions
The bot's design note on PR #672 flagged a regression: bare `add` in the
risk gate matched ordinary CRUD wording like "How should users add a
task?", false-blocking selected-driver sessions under brake=on.
Replace bare `add` with `add(?:ing)?\s+(?:a|an|the)?\s*<scope-noun>`
where the scope-noun is feature/capability/support/requirement/epic/
story/scope/product-area. CRUD verbs no longer match while genuine
scope-additions ("Should we add a feature for offline mode?") still
fire the gate.
Refs #672
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(auto): align selected-driver ledger values with the freeform answer
The bot's blocking finding on PR #672 noted that the selected-driver
path sent the driver's freeform answer into the interview transcript
but kept the deterministic scaffold's value in ``ledger_updates``.
Seed generation reads the transcript while grading reads the ledger,
so the two could disagree silently (driver says "Django", ledger says
"FastAPI") without anyone catching the divergence.
- Replace each scaffold-derived ledger entry value with the driver's
freeform answer verbatim and tag the entry CONFLICTING with reduced
confidence (<= 0.4), so the Seed-ready/A-grade gates surface the
divergence instead of treating the scaffold value as confirmed.
- Preserve the structural section/key/source so downstream
section-aware Seed generation still works, and keep the original
scaffold value in the rationale + evidence as audit context.
- Update the existing ledger-values test to lock in the new contract
and assert the original scaffold value is preserved as rationale
evidence.
Refs #675
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(auto): lock packaged driver/brake forwarding at MCP payload layer (#679)
Issue #673 acceptance criteria require that the actual MCP payload reaching
ouroboros_auto carries forwarded driver/brake values and never leaks $driver
or $brake placeholder literals. Upstream stack/3 already locks dispatch-level
resolution; this commit adds the missing layer by mocking the ouroboros MCP
server and asserting call_tool's payload.
- Forwarding test: --driver hermes --brake off must reach call_tool with
driver="hermes", brake="off", skip_run=True.
- Placeholder leak test: plain `ooo auto "goal"` must not send "$driver" or
"$brake" as real values; an empty/None value is acceptable.
Closes #673
* fix(auto): use INFERRED status for driver-derived ledger entries
The earlier fix that aligned ledger values with the driver's freeform
answer marked every structural ledger update as ``LedgerStatus.CONFLICTING``.
The interview loop treats CONFLICTING (along with MISSING/WEAK/BLOCKED) as
an open gap (``ledger.py:open_gaps``), so a selected-driver session could
populate every required section and still never reach ``is_seed_ready`` —
the loop would carry the same gaps forever and eventually block.
Use ``LedgerStatus.INFERRED`` instead. The ledger entry still:
- Carries the driver's freeform answer verbatim as the value, so the
persisted ledger and the interview transcript share the same content
(no silent divergence between the two sources of truth).
- Has reduced confidence (<= 0.4) and an ``auto_interview_transcript``
evidence marker so grading and the A-grade gate can downgrade or
re-verify the driver answer before final acceptance.
- Preserves the original scaffold value verbatim in the rationale and
in a ``scaffold_value:<value>`` evidence tag, so divergence between
scaffold and driver is never silently lost.
INFERRED is the right semantic: the value is the driver's inferred answer,
not the user's confirmed choice; downstream grading is responsible for
deciding whether to escalate to verification before A-grade. The interview
loop is now free to converge for selected-driver sessions.
Tests:
- ``test_driver_answerer_ledger_values_reflect_driver_answer_without_blocking_loop``
asserts the new INFERRED+verbatim+scaffold-evidence contract and locks
in that the status is not in the loop's blocking set.
- ``test_driver_answerer_ledger_does_not_block_seed_ready_convergence``
is a regression test that drives the answerer through every required
section and asserts those sections do not end up in the open-gap set
(the contract that broke under the CONFLICTING variant).
Addresses ouroboros-agent[bot] blocking finding on PR #672 against
``f229e35``. Refs #672.
* feat(auto): add selected-driver answer metadata (#682)
Co-authored-by: Hermes Agent <hermes-agent@users.noreply.github.com>
Co-authored-by: shaun0927 <junghwan1912@gmail.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(auto): align mcp resume bounds (#680)
Co-authored-by: Hermes Agent <hermes-agent@users.noreply.github.com>
---------
Co-authored-by: shaun0927 <junghwan1912@gmail.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: Junghwan <70629228+shaun0927@users.noreply.github.com>
Co-authored-by: Hermes Agent <hermes-agent@users.noreply.github.com>1 parent 76475a5 commit d61df30
19 files changed
Lines changed: 2007 additions & 18 deletions
File tree
- skills/auto
- src/ouroboros
- auto
- cli/commands
- config
- mcp/tools
- tests/unit
- auto
- cli
- config
- router
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| 12 | + | |
| 13 | + | |
12 | 14 | | |
13 | 15 | | |
14 | 16 | | |
| |||
30 | 32 | | |
31 | 33 | | |
32 | 34 | | |
| 35 | + | |
33 | 36 | | |
34 | 37 | | |
35 | 38 | | |
| |||
42 | 45 | | |
43 | 46 | | |
44 | 47 | | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
9 | | - | |
| 9 | + | |
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
| |||
17 | 17 | | |
18 | 18 | | |
19 | 19 | | |
| 20 | + | |
20 | 21 | | |
21 | 22 | | |
22 | 23 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
| 21 | + | |
21 | 22 | | |
22 | 23 | | |
23 | 24 | | |
| |||
64 | 65 | | |
65 | 66 | | |
66 | 67 | | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
67 | 77 | | |
68 | 78 | | |
69 | 79 | | |
| |||
75 | 85 | | |
76 | 86 | | |
77 | 87 | | |
| 88 | + | |
78 | 89 | | |
79 | 90 | | |
80 | 91 | | |
| |||
0 commit comments