Document pre-teach rewrites, the demand scan, and per-level comment decks Roadmap and Use-Cases note the rewrite suggestions from structure-rewrites.csv, the Demand scan table in the set summary, and the per-level rubric-comment decks (rubric at a construction's own level, pre-teach above it); the contract is 1.3. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Document the class-level filter on grammarComments Roadmap and Use-Cases note that under a target, --comments filters the grammar half to the class level: at/below constructions keep their pass/fail comments, used above-target ones become pre-teach-or-rewrite notes, unused ones drop; the contract is 1.2. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Document the vocabulary half of the apply-as-comment pass Roadmap and Use-Cases note that --comments now covers the whole report: vocabComments (per above-target word) alongside grammarComments, and the payload contract version is 1.1. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Phase 5: apply-as-comment reference implementation Roadmap: the per-criterion grammar pass/fail item now notes the shipped reference implementation — analysis.grammar_comments turns grammarCriteria into one rubric comment per construction, carried as grammarComments under --comments and rendered as a Rubric comments handout section. Use Cases: scenario 13 covers grammarComments with --comments. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Phase 5: versioned report contract + per-criterion grammar pass/fail Roadmap: stable library / JSON contract and the per-criterion grammar pass/fail item marked shipped — every payload carries schemaVersion, the JSON Schema is checked in (analysis.schema.json, kept in sync), and grammar-enabled payloads carry grammarCriteria (per-construction used / not used + pass/fail) for RubricMaker's grammar linker. Use Cases: scenario 13 — the app consumes the report contract. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Phase 4: grammar-item validation in the curriculum checklist 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Phase 4: --cando-diff-sort band ordering 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Phase 4: set-level Can-Do diff, Can-Do reference decks, curriculum schema validation 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Phase 4: Can-Do per text + target diff, curriculumCoverage in the JSON payload 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Phase 4: Can-Do framing, summary-handout curriculum grid, interleave-aware pre-enrich 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Ship the coverage grid, folder watch mode, and Cambridge exam mapping
Ship watch mode and the curriculum checklist; rewrite use case 7
Ship vocabulary interleaving: mark it done on the roadmap and add use case 12
Mark Phase 3 highlight + synonym suggestions as shipped; update the graded-reader use case Roadmap: Phase 3 is now in progress with the first two items shipped — above-target highlighting (text_report + class profile) and simpler-synonym suggestions (text_report.py --suggest with the curated WordLists/synonyms.csv). Use Case 6 shows the rewrite loop with --suggest naming the swaps.
Document Phase 2: class-profile tool, roadmap, use cases, RubricMaker alignment Home now lists all four tools; the roadmap marks Phase 2 (class set, not one text) as shipped with the delivered feature set; use cases 5, 9, 10 show the one-command replacements and a new use case covers 'which of these suits B1?'; the RubricMaker alignment table flips the dashboard/document-analysis rows to shipped.
Add use cases, roadmap, and RubricMaker alignment