Surveyor misses live Bugbot requests when a connector adds a footer #606

🤖 Generated by the Agentic Engineer

Problem

The surveyor pairs a Bugbot request marker only with the next exact-author bare trigger. A request with a connector-added footer starts the same review but is invisible to this pairing rule, so another instance can request a duplicate review at the same head.

Reproduced evidence

At main c759182ac59d550f8d1f3d5b03d86f2fa0e79b06, the surveyor definition still requires a bare trigger. In the consuming deployment, the actual marker check's complete regression suite passes first-line commands with trailing text or a footer, and rejects a command below the disclosure line. This run independently exercised those cases. The contradictory definition remains in the consumer overlay and review guide (devantler-tech/monorepo#3955).

Intended outcome

Use the same conservative trigger boundary for request accounting: the next exact-author comment whose first nonblank line names the command. Keep the authenticated disclosure, exact author, provider and full-head marker requirements; a request marker or counted trigger ends the pairing window. Interleaved other-author comments remain ignored. This changes observation and deduplication only: emitted requests remain the canonical bare trigger, and review findings and readiness gates remain mandatory.

Acceptance

• The portable surveyor describes the first-line boundary, including connector footers and trailing text.
• A command below a disclosure line neither pairs nor closes the pending marker window.
• A focused regression rejects a return to bare-only pairing and protects the authentication, head and window boundaries.
• Bump the plugin's cache version through its supported writer and validate manifests, tests and the resulting installed package before protected merge.
• Consume the merged definition in monorepo#3955; upstream source delivery alone does not finish that deployment issue.