feat(config): lane map moves to .cursor/models.yaml, shared schema — 0.3.0 #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/models-yaml-lane-map"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
models:block lived insideimplementation-skills.yaml, where neither sibling edition could read it. The lane map moves to.cursor/models.yamlusing the schema shared verbatim with the Claude Code and Codex variants;implementation-skills.yamlkeeps tracker, gate, merge, deploy and policy.A pre-0.3
models:block is still read, andisc doctorreports that it has moved.iscfixes found by adversarial review: one strictly flat parser for the lane map (separate from the operational config's richer subset), explicit source variables so a path containing a space resolves instead of silently falling through to defaults, a framed render stamp (moving a key between files changes resolution and previously could leave a byte-identical digest and a green doctor on stale agents), both reviewer lanes checked plus the cheap-lane invariant, failures instead of warnings, exact roster matching, and--globalas a real scope forinitandsync.47 executable checks in
tests/isc-smoke.sh.