Skip to content

#57 fix: CR round 1 — the escape clause names co-core's resolvers; readable guard ids - #61

Merged
gregoryfoster merged 2 commits into
mainfrom
57-cr-round1
Oct 21, 2026
Merged

gregoryfoster merged 2 commits into
mainfrom
57-cr-round1

Conversation

@gregoryfoster

Copy link
Copy Markdown
Contributor

Refs #57. Review round 1 of #60 (a1a9e91..359e102), both findings 💭, one commit each.

Item Action Result
1 Fixed 85c499a: spec §5 and the tests/test_pin.py docstring now say the rule reverts if Processor calls co-core's resolvers (resolve_dispatch_essence, extension_media_type). That is what the guard checks. Resolving any other way is Section 3's to forbid, and a co-core bump wouldn't move it.
2 Fixed 18deb3c: the guard's self-test cases have ids (from-import … dispatch-call), not raw source strings.

Gate: ruff check and format clean, uv lock --locked clean, 696 passed, 14 skipped. The skips are environmental: the worktree has no .env, and /etc/processor is unreadable as exedev.

No deploy: only docs/ and tests/ change.

Known gap, not fixed here: the posted Watcher notice (watcher#368) and #57's closing comment use #60's broader wording ("if Processor ever resolves essences itself, the test fails"). Editing the watcher comment would need approval.

🤖 Generated with Claude Code

gregoryfoster and others added 2 commits October 21, 2026 19:22
…rs, as the guard checks

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant