docs: reconcile the bounded application build frontier - #206
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (4)
🧰 Additional context used📓 Path-based instructions (5)Tests must assert software behavior and stable error kinds or structured artifacts, not implementation details, prose, paths, or merely `is_err()`; documentation-tool tests may test validator behavior.📄 CodeRabbit inference engine (AGENTS.md) Files:
Never amend Git commits, use `git rebase` without explicit user approval, or force any Git operation; use new commits and regular merge commits instead.📄 CodeRabbit inference engine (AGENTS.md) Files:
Topic shelves document landed behavior: `README.md` describes current HEAD truth, `test-plan.md` records verification and known gaps, and optional architecture or rationale pages contain durable supporting information.📄 CodeRabbit inference engine (AGENTS.md) Files:
Documentation pages must have one primary reader job, separate user task help from contributor architecture and evidence maps, use concrete valid examples with expected results when relevant, and keep exact public facts in validated or gene...📄 CodeRabbit inference engine (AGENTS.md) Files:
Use tables for consistent-shape comparisons and evidence, bullets for unordered sets, numbered lists for ordered procedures or states, and focused branch-accurate snippets for exact syntax.📄 CodeRabbit inference engine (AGENTS.md) Files:
🪛 LanguageToolROADMAP.md[grammar] ~62-~62: Ensure spelling is correct (QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1) 🔇 Additional comments (2)
Summary by CodeRabbit
WalkthroughThe roadmap now uses bounded application-build evidence as its current frontier. It records delivered foundations, remaining evidence work, and unsupported runtime or publication activities. The public Rust API test plan updates two requirement references from issue ChangesBounded application-build evidence
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This updates planning and requirement references without changing product behavior. No current merge-readiness risk remains. 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
Full details: Linked Issues checkExplanation The PR updates the roadmap frontier as required by
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. The roadmap sheds its dated crown Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
1 participant
Plain-English Walkthrough
TL;DR
The roadmap still named a provider milestone that closed on July 13. It now points to the bounded application-build acceptance work in Edict #192 and the real Jedit consumer in Jedit #296/#302. [claim:current-frontier, confidence:0.99]
The curated facade requested by #189 has shipped and that issue is closed. Planned package inventory and independent packaged-consumer evidence now reference #204; the optional live frontier-state checker from #187 is tracked separately in #205. [claim:scope-split, confidence:0.99]
Walkthrough
A reader choosing the next Edict task starts at Current Frontier. The old section described the completed Provider Artifact Pipeline Alpha and called #147 current. The replacement keeps the completed milestone as historical evidence, links the owning shelves for delivered compiler/library contracts, and identifies the remaining acceptance work. GitHub owns the detailed checklists and current PR status. [claim:roadmap-routing, confidence:0.99]
The frontier distinguishes the real consumer's accepted package from runtime execution: the current ReplaceRange source constructs a typed boundary result, while the rope algorithm and generic Echo evaluator remain downstream work. Echo #724 is an open provider candidate. No new release milestone, publication decision, or runtime capability is declared. [claim:consumer-boundary, confidence:0.99]
The public Rust API test plan keeps its implemented facade requirement tied to #189 and moves only the two already-planned package requirements to #204. Their status remains planned. Automated comparison with GitHub state is also explicitly planned in #205. [claim:planned-evidence, confidence:0.99]
Validation and documentation impact
cargo xtask verify: passed: 898 tests in 51 groups, strict all-target/all-feature Clippy, 27 topic shelves, CLI/provider/golden checks.cargo test -p edict-syntax --test compiler_spine --test lawpack: 80 compiler-spine and 58 lawpack tests passed on base main3f81f759e921a69b04fe8cf8e62e62f8f3dc7b7e.cargo test -p flyingrobots-edict: four integration tests and two doctests passed on that base.2026-07-13T07:51:17Z.git diff --check: passed.No RED/GREEN cycle was required: this corrects roadmap and evidence ownership metadata, with no compiler, API, schema, workflow, or validation behavior change. No tests assert documentation wording.
docs-impact: Current Frontier and two source references updated; owning contract READMEs and executable tests remain accurate and unchanged. No dependencies or release artifacts changed.Appendix: Citations
claim:current-frontier,claim:roadmap-routingROADMAP.md#30@404e77ef297ca765f556dd5ee579268ae65abfa6; closed provider milestone; #192claim:scope-split,claim:planned-evidencedocs/topics/public-rust-api/test-plan.md#25@404e77ef297ca765f556dd5ee579268ae65abfa6; #189 disposition; #204; #205claim:consumer-boundaryedict/replace-range/README.md#18@a894c7c4c6d150c0fb210d2e0ca4c27bf518b4c7; Jedit #302; Echo #724Closes #187