Implement CR-DD-016: capability-probe operator workflow discoverability - #157
Merged
Merged
Conversation
Bounded implementation of the corrected requirements contract (CR-DD-016, after its #155 scope repair and #156 causal-claim correction). Exactly the four-path Implementation Allowlist, nothing else. - docs/daily_driver_quickstart.md: new "Understand local-capability probing" section documenting the three-case contract (declaration+ binding alone permits route consideration; a fresh probe upgrades the evidence tier or conclusively overrides on a negative result; neither usable fails local_only closed) and the 300-second freshness consequence. - triage_core/tc_cli.py: tc probe --output argparse help text now names [capability].local_probe_record_path as the required follow-up config key. Help/description text only -- no flag shape, default value, command dispatch, or execution path change. - tests/test_tc_cli.py: one focused regression test asserting the help text names the config key and explains --output has no effect on tc run by itself. Compares against whitespace-normalized output and pins COLUMNS explicitly so the assertion doesn't depend on ambient terminal width (verified failing before that fix, at both default and artificially narrow widths). - CR-DD-016 doc: implementation evidence, allowlist marked drafted, all acceptance criteria checked. Status stays short of "complete" -- implementation is drafted and verified on this branch, PR review and merge into main are still pending; implementation authority is exercised within the four-path allowlist but not yet closed out. No change to capability resolution, routing, probe behavior, config defaults, or persistence semantics. Focused suites 72/72 (test_tc_cli.py, test_capability_binding.py, test_tc_run_cli.py); full suite 1669 passed, 6 skipped, 0 failed.
✅ Deploy Preview for poetic-quokka-0fd859 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
The prior wording ("PR open, not yet merged", "still-pending human
gate") was accurate on the branch but would read as false the instant
this PR merges into main. Rephrase so the same text is true both
before and after merge:
- Status: completion is defined by merge, not asserted or denied.
- Implementation authority: "exercised... no further changes
authorized... once merged, spent" holds in both states.
- Implementation evidence: identify commit 01e8b14 / PR #157 instead
of describing branch state.
- Rename "Implementation Allowlist (Drafted -- Pending PR Review and
Merge)" to "Authorized Implementation Allowlist" and drop the
open-PR sentence.
No implementation change. Avoids a follow-up status-fix PR after #157
lands.
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
The bounded implementation of CR-DD-016, after its requirements contract survived two
rounds of correction (#155 scope repair, #156 causal-claim correction). Exactly the
four-path Implementation Allowlist named in the CR doc — nothing else.
Not a merge/complete claim. This PR is the implementation candidate. The CR doc's
own Status section explicitly stays short of "complete": implementation is drafted and
verified on this branch, but the CR is not considered done until this PR is reviewed and
merged. That is a separate, still-pending human gate after CI.
What changed
docs/daily_driver_quickstart.md— new "Understand local-capability probing"section documenting the three-case contract: a
[capability]declaration with aresolved model binding permits route consideration by itself; a fresh probe upgrades
that to a checked observation (or conclusively overrides it on a negative result, or
catches a model-name mismatch); with neither usable,
local_onlyfails closed. Alsostates the 300-second freshness consequence.
triage_core/tc_cli.py—tc probe --output's argparse help text now names[capability].local_probe_record_pathas the required follow-up config key. Text only:no flag shape, default value, command dispatch, or execution path change.
tests/test_tc_cli.py— one focused regression test,test_tc_probe_help_names_capability_probe_record_path, asserting the help text namesthe config key,
triagecore.toml, and explains--outputhas no effect ontc runbyitself. Compares against whitespace-normalized output and pins
COLUMNS=200explicitly, so the assertion doesn't depend on ambient terminal width (verified failing
before that fix, both at the default width and at an artificially narrow one where
argparse wrapped mid-identifier).
drafted/pending, all acceptance criteria checked against what was actually verified.
What did not change
No file outside the four listed above. No schema, CLI flag shape, default value, command
dispatch, probe execution, capability resolution, routing decision, persistence behavior,
or runtime semantics change.
triage_core/local_backend_probe.py,capability_evidence.py,config.py,client.py, androuting/resilience_router.py—the CR's own named exclusions — are untouched.
Verification
git status --short(staged)git diff --checktest_tc_cli.py,test_capability_binding.py,test_tc_run_cli.py)🤖 Generated with Claude Code