fix(marketing): label unimplemented walkthrough checks

[SHAURYAKSHARMA24]

Summary

Label every speculative finding as proposed and unimplemented, correct limited category coverage, and stop counting proposals as emitted analyzer findings. Add CI parity tests.

Linked issue

Related to #528.

Scope

Audit F1; baseline dev df0e82be3d7b2b7d846eefc1bcf82bde834936f2. This corrects independently verified existing behavior and advances the linked issue without adding product scope.

What changed

Label every speculative finding as proposed and unimplemented, correct limited category coverage, and stop counting proposals as emitted analyzer findings. Add CI parity tests.

Acceptance criteria completed

Implementation and targeted regression coverage below. See remaining work for conditions not verified.

Testing performed

Two semantic demo/capability parity tests, lint and build passed; actual Chromium journey confirms four proposed-check labels. Desktop/mobile screenshots captured and inspected. UTF-8 text correction verified.

Current head: 093150e53e40a9e26afa49916407b9e49ce63902; check snapshot appears below.

Screenshots

Local screenshots and browser measurements are recorded in the remediation delivery report where applicable. Backend-only changes use contract/regression evidence.

Security and data considerations

Preserves owner scoping, source provenance, sealed graph contracts and historical data. No security gate weakened. Rollback: revert this scoped commit; see issue for migration/deployment implications.

Dependencies and blocked work

Independent dev-based PR unless explicitly stated in the issue. No unmerged changes included.

Scope changes or remaining work

Required current-head CI and maintainer review.

Please review @parthrohit22.

Contributor checklist

• Targets dev; dedicated fork branch from latest dev; issue claimed.

• Scope/evidence recorded; unrelated changes and secrets excluded.

• Targeted validation results reported accurately.

• Required current-head CI and maintainer review complete.

Current-head remediation validation

Head: 093150e53e40a9e26afa49916407b9e49ce63902.

Two semantic demo/capability parity tests, lint and build passed; actual Chromium journey confirms four proposed-check labels. Desktop/mobile screenshots captured and inspected. UTF-8 text correction verified.

Required current-head CI and maintainer review.

Checks at delivery: Repository Hygiene: SUCCESS; Analyze (javascript-typescript): SUCCESS; Analyze (python): SUCCESS; API Contract Drift: SUCCESS; Frontend: FAILURE; Backend: SUCCESS; Docker Build: SUCCESS; Marketing Site: SUCCESS; Prototype Browser Acceptance: SKIPPED; Vercel: FAILURE; CodeQL: SUCCESS. Required checks/reviews must pass before merge; deployment authorization was not granted.

[vercel]

@SHAURYAKSHARMA24 is attempting to deploy a commit to the parthrohit60-3117's projects Team on Vercel.

A member of the Team first needs to authorize it.

[SHAURYAKSHARMA24]

Additional validation

Actual Chromium demo journey completed and displayed all 4 proposed-check labels; desktop/mobile screenshots captured and inspected.
No merge or public deployment performed.