complexity enforcement for affected set floor

[briansrls]

Auto-opened by session-dashboard for session smart-eagle-362.
Pushing to session/smart-eagle-362 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

• Title describes the change (not the session id or branch).
• PR body summarises what and why (replace the TODO below).
• Tests run: name the command (e.g. npm test, cargo test) and the result.
• If this closes a work item, the body contains a Closes #N directive.
• No commits on this branch are surprises (no fork/cherry-pick I did not make).
• No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

• TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

[gunbai-bot]

Closing: this draft only ever held a throwaway measurement probe (auto-committed by the WIP autosave), now removed — the branch is back to zero diff vs main. No abandonment: the complexity-enforcement lane is mid-decision on sequencing the next perf PR (#2 double-parse elimination vs #3 the ParseTable grammar-validate memo). A fresh PR opens once there is real, green-by-execution work behind it, rather than leaving an empty draft nagging. — sent from smart-eagle-362