Live proving round on Forge surfaced two proposer precision gaps (milestone 294, #2792 follow-up):
- signature basis compared against the canon code's *first* definition (often a call-site example), now only the canon's own-symbol definition
- semantic floor 0.68 → 0.8
- `_PROPOSER_VERSION` folded into `proposed_sha` so standing proposals from the older ruleset are re-examined on the next refresh
dev CI 4124 green.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
First live run: a canon whose recorded code opens with a call-site example
(confirmed()'s onTrash) made every `async function x(): Promise<void>`
resemble it at 0.86, and the write-path semantic floor paired alembic
upgrade()/downgrade() bodies with unrelated canons at 0.68-0.75. Rows now
remember (body, ruleset) so a tightened rule looks again once.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Live proving round on Forge surfaced two proposer precision gaps (milestone 294, #2792 follow-up):
_PROPOSER_VERSIONfolded intoproposed_shaso standing proposals from the older ruleset are re-examined on the next refreshdev CI 4124 green.
🤖 Generated with Claude Code