eval: cover Agent Spec launch method selection - #71
Draft
schickling-assistant wants to merge 1 commit into
Draft
Conversation
agent-tool: Codex agent-tool-version: 0.145.0 agent-runtime: Codex 0.145.0 agent-session-lookup: unavailable tooling-profile: dotfiles@unknown-dirty
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
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.
Problem
The proposed Agent Spec start/resume lifecycle has no model-free behavior cell covering method selection, exact-session continuation, unavailable-method policy, and compatibility with the existing single
argvform.Goal
Add contract-first expected-red coverage for the proposed syntax while keeping the current portable runner and canonical
AGENT-SPEC.mdunchanged.Decisions
argv.RED/P01against the published runner. Expected reds are classified evidence, not conformance passes.AGENT-SPEC.md.Verification
0fed14b: four proposal casesRED/P01, legacy casePASS,PRODUCT-RED, zero residue; 5/6 judges pass and the run step fails as intended.add61394c335092eaed6d85e00d7befe8b05c023: all five behavior cases pass,PRODUCT-GREEN, zero residue. The outer eval fails only the deliberately frozen current-runner classification map.bash cells/launch-method-selection/judges/self-test.sh: 6/6 contract mutations rejected.git diff --checkpass.bin/check-corpus.shremains red on the unchangedweird-git-setupfixture: its intentional alternate commit identity is rejected by the globally installed assistant-identity commit hook. The fixture and check are unchanged frommain, and the failure predated this change. The hook was not bypassed.Complexity
Medium. The cell is model-free, but it exercises five isolated catalogs and adversarial synthetic session records with explicit cleanup.
Concerns
resume.session; upstream model tests own that assertion.Friction & bottlenecks
The repository did not ignore the
tmp/directory used by the required Axe worklog. This PR adds the missing ignore rule so local tooling metadata cannot enter the publishable PII surface.Follow-ups
When a ratified implementation becomes the published eval runner, update the frozen case manifest from the four
P01expected reds to the accepted behavior map.References
Refs compoundingtech/st2#124.