Align Week 2 checker scope

[Abiorh001]

Summary

• add a Week 2 checker framework scope/spec document
• clarify Week 2 is backend/checker-framework only, not product frontend or review UI work
• replace task-page/reviewer-visible wording with API/dry-run visibility wording
• clarify checker failures are gates, not accept/needs_revision/reject review decisions

Verification

• stale wording scan only hits the intentional banned-word guardrail in AGENTS.md
• Markdown links OK
• no local XLSX export present
• git diff --check

Summary by CodeRabbit

• Documentation
  • Added Week 2 Checker Framework Specification document
  • Updated architecture and roadmap documentation with clarified checker control-flow and scope boundaries for automated submission validation
  • Refined execution plans and backlog tracking with explicit checker binding and API exposure requirements

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 192be903-a885-46e1-a46b-45a7205ff0bb

📥 Commits

Reviewing files that changed from the base of the PR and between a08a521 and 2ffa1ea.

📒 Files selected for processing (7)

• README.md
• docs/architecture_checker_framework.md
• docs/roadmap_30_day_master_plan.md
• docs/roadmap_day_by_day_execution_plan.md
• docs/roadmap_implementation_backlog.md
• docs/roadmap_status.md
• docs/spec_week2_checker_framework.md

---

📝 Walkthrough

Walkthrough

This PR adds a Week 2 Checker Framework Specification document and updates supporting architecture, roadmap, and planning documentation to define and align execution around how automated checkers bind to locked submissions, gate entry to REVIEW_PENDING, and constrain scope to backend API exposure.

Changes

Week 2 Checker Framework Documentation

Layer / File(s)	Summary
Week 2 Checker Framework Specification (New Document) docs/spec_week2_checker_framework.md	New comprehensive spec document defining the checker boundary: tasks cannot reach REVIEW_PENDING without completed checker runs tied to exact submission/artifact hashes; checker decisions are blocking vs non-blocking (not acceptance/rejection); Week 2 exposes results via backend APIs and dry-run/demo output (not product frontend pages); chunk deliverables span records/contracts, runner/registry, evidence/policy checkers, pre-review gate enforcement, and trial documentation; verifier roles include senior engineering, QA/test, security/auth, and product/ops.
Architecture Control-Flow Refinement docs/architecture_checker_framework.md	Clarifies checker-run flow: runs bind to immutable submission versions with automatic reruns on replacement uploads; failures block review entry without creating review decisions; outcomes lead to REVIEW_PENDING or remain blocked until worker submits replacement, records override, or later workflow handles the issue.
Roadmap and Execution Planning Updates docs/roadmap_30_day_master_plan.md, docs/roadmap_day_by_day_execution_plan.md, docs/roadmap_implementation_backlog.md, docs/roadmap_status.md	Aligns all roadmap documents with the spec: Week 2 is backend-focused with API-readable results including exact submission/version and artifact hash manifests; high-severity failures block REVIEW_PENDING without creating review decisions; Days 6–10 now specify binding invariants (submission id/version/package/artifact hashes), evidence/artifact-hash gating, locked task policy context, and Week 3 reviewer visibility; backlog restructured with separate items for API-readable results, worker failure summaries, and split binding requirements; status document marks spec as completed and refines pending checker-contract/record tasks.
Planning Package Reference Update README.md	Adds the new Week 2 Checker Framework Specification to the Planning Package section.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Flow-Research/workstream#8: Both PRs update the Week 2 checker framework documentation by changing the checker gating/contracts around policy context and checker-run outcomes (e.g., docs/architecture_checker_framework.md introduces/adjusts required policy-context checkers while the main PR specifies how checker results bind to locked submissions/versions and gate REVIEW_PENDING).

Poem

🐰 A spec for checkers takes its place,
Binding submissions, case by case,
REVIEW_PENDING locked and gated tight,
Backend APIs shine with light,
Week 2's framework, clear and right! 🎯

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Align Week 2 checker scope' directly corresponds to the main objective of the PR, which is to add and clarify Week 2 checker framework documentation and align the scope across multiple documents.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch align-week2-checker-scope

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}