Add an opt-in GuideCheck 2.0.0 corrected content profile

[snapsynapse]

Problem

Released GuideCheck profiles preserve frozen content behavior. The corrected detector and bounded-execution rules need an explicitly selected profile so unchanged guides and legacy reports keep their existing meaning.

Scope

Implement the proposed 2.0.0 profile across the normative profile, schemas, fixtures, local CLI, hosted evaluator, reports, and UI. Keep selection driven by the guide's declared profile version and preserve the released legacy and 1.0.0 paths.

Acceptance conditions

• A guide selects the corrected policy only by declaring profile-version: 2.0.0; caller flags and manifest-only changes cannot reinterpret old guide bytes.
• Frozen legacy replays and all released 1.0.0 fixtures remain unchanged.
• The corrected negation, independent-occurrence, and execution-target cases have static regression coverage.
• An unresolved effective execution target blocks Level 3 even when the action declares a hash.
• Repository-file evidence remains corroboration and cannot qualify a 2.0.0 guide for Level 4.
• Local and hosted evaluation report the same selected content and anchor policies for equivalent evidence.
• Schemas, version checks, and the full repository test suite pass.

Release, deployment, and adopter migration remain separate delivery steps.

[snapsynapse]

Implemented by merged PR #3 at 2554851e66a14762a99df8c7c341dc79d9aadd47.

All issue acceptance conditions are satisfied: guide-byte-only profile selection; unchanged full legacy/1.0.0 report replays; static corrected-content and execution-target regressions; blocking unresolved execution even with a declared hash; repository evidence excluded from Level 4 qualification; matching local/hosted selected policies; passing schemas, version checks, and full tests.

Main CI passed on that exact merge commit: https://github.com/snapsynapse/guidecheck/actions/runs/34174595065. PR #3 includes isolated installed-wheel, authenticated preview, hosted dispatch, and UI evidence. Production's deployment manifest identifies the same merged commit.

Closing as completed at this issue's implementation boundary. The owner has separately approved final 2.0.0 release metadata, production integration, and signed release delivery, which are being completed separately. Existing DNS-anchor and A11y consumer-guide findings remain independent maintenance work; no adopter or frozen report was migrated.