docs: reconcile the bounded application build frontier

[flyingrobots]

Plain-English Walkthrough

TL;DR

Replace the completed Provider Artifact Pipeline Alpha frontier with the current bounded application acceptance boundary. The roadmap now reflects merged Jedit #302 as a working pure flat-text reference and points to full application acceptance in #296 and the unfinished Echo #921 effect bridge. [claim:frontier, confidence:0.99]

Walkthrough

Readers choosing the next compiler task previously encountered a completed provider milestone and an outdated typed-boundary-only description of Jedit. The new section links landed compiler foundations, separates pure package execution from persistent graph edits and settlement, and retains the unfinished packaged-facade and live-reference-checker work. Closed Edict #192 and #203 are recorded as closed. The historical provider #724 is not presented as the current candidate. [claim:scope, confidence:0.99]

The public Rust API plan moves only two planned package-closure requirements from the delivered facade issue #189 to open #204. Their planned status is unchanged. [claim:package-plan, confidence:0.99]

The branch incorporates current main by a regular merge. This is a documentation-only correction; compiler behavior, package identities, release policy and dependencies are unchanged by the PR diff. No RED/GREEN cycle applies, and no tests assert prose. Docs-impact is the roadmap and the two requirement-owner references. [claim:docs-only, confidence:0.99]

Validation

At 6f16ea4, cargo +1.96.0 xtask contract-check passed for 28 topic shelves and git diff --check passed. Live GitHub readback confirmed #192 and #203 closed, #204 and #205 open, and Jedit #296 open. The full local cargo +1.96.0 xtask verify gate also passed on this head, including format, strict all-feature Clippy, workspace tests, CLI/provider/golden checks, contract checks and diff validation. All hosted checks are green; CodeRabbit approved 6f16ea4 and there are zero unresolved threads.

Appendix: Citations

Claim	Evidence	Confidence	Notes
claim:frontier, claim:scope	ROADMAP.md#30@6f16ea4; merged Jedit #302; open Jedit #296; Echo #921	0.99	Current landed pure reference is distinct from unfinished persistent effects and settlement.
claim:package-plan	docs/topics/public-rust-api/test-plan.md#26@6f16ea4; Edict #204	0.99	Both requirements remain planned.
claim:docs-only	PR diff against main at 6f16ea4	0.99	Two Markdown files only.

Closes #187

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-19T06:39:17.611581Z	6f16ea4	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: c5f8da21-8421-446f-964a-e7f5bc9e4f37

📥 Commits

Reviewing files that changed from the base of the PR and between 404e77e and 6f16ea4.

📒 Files selected for processing: 2

• ROADMAP.md
• docs/topics/public-rust-api/test-plan.md

Included review availability: This review used your included allowance. 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: 5

• GitHub Check: rust stable (fmt · clippy · test)
• GitHub Check: rust msrv 1.96.0 (fmt · clippy · test)
• GitHub Check: windows lawpack containment
• GitHub Check: supply-chain (cargo-deny)
• GitHub Check: release-dates (git tag reconciliation)

🧰 Additional context used

📚 Code guidelines: 2

AGENTS.md — configured
docs/topics/documentation/README.md — auto-discovered

📓 Path-based instructions: 2

Source excerpt: Do not churn topic shelves for purely mechanical edits that do not change a contract, such as formatting, typo fixes, dependency pin updates with no observable behavior change, or internal refactors whose existing tests and...

📄 CodeRabbit inference engine (AGENTS.md)

Files:

• docs/topics/public-rust-api/test-plan.md

Applicability reference: AGENTS.md: # AGENTS Follow the canonical [durable decision policy](docs/topics/documentation/README.md#durable-decision-discipline).

📄 CodeRabbit inference engine (docs/topics/documentation/README.md)

Files:

• docs/topics/public-rust-api/test-plan.md

🔇 Additional comments: 2

ROADMAP.md: 1

40-41: LGTM!

Also applies to: 60-76, 83-85

docs/topics/public-rust-api/test-plan.md: 1

26-27: LGTM!

Also applies to: 29-29, 41-41

Summary by CodeRabbit

• Documentation
  • Updated the roadmap to mark the Provider Artifact Pipeline Alpha milestone complete and identify the next acceptance boundary.
  • Documented delivered compiler and library foundations, remaining work, and follow-up items.
  • Noted that evidence is not recorded for runtime execution, admission, registry publication, or release tagging.
  • Updated public Rust API test-plan references to the latest tracking issues.

Walkthrough

The roadmap replaces the Provider Artifact Pipeline Alpha frontier with bounded application-build evidence. It records delivered foundations, remaining acceptance and package-closure work, and activities that still require separate evidence. The public Rust API test plan changes two requirement references from issue #189 to issue #204.

Changes

Bounded application-build evidence

Layer / File(s)	Summary
Frontier and delivered foundations ROADMAP.md	The roadmap marks the Provider Artifact Pipeline Alpha milestone complete, names Jedit #296/``#302 and Edict #192 as the next acceptance boundary, and lists delivered compiler and library foundations.
Remaining evidence and source references ROADMAP.md, docs/topics/public-rust-api/test-plan.md	The roadmap tracks remaining compiler, Jedit and Echo acceptance, package closure, and GitHub-state comparison. It states that runtime execution, admission, registry publication, and release tagging still require separate evidence and decisions. The test plan updates two requirement references from issue #189 to issue #204.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 6f16e

The roadmap update and test-plan reference changes leave no actionable merge risk; automated GitHub-state comparison remains clearly identified as planned follow-up.

### Architecture Summary

Architecture risk: 🔵 Low · up to 6f16e

The change affects 2 systems.

Changed systems: docs, ROADMAP.md

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — docs (service) was modified; 1 changed file maps to changed impact.
• observed — ROADMAP.md (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in ROADMAP.md: Replaced the Provider Artifact Pipeline Alpha frontier with a bounded application-build evidence frontier. The new text marks the former milestone complete, names Jedit #296/``#302 and closed Edict #192 as the next acceptance boundary, and distinguishes GitHub tracking from topic-shelf contract descriptions.
• observed — Modified behavior in ROADMAP.md: Added an inventory of delivered compiler and library foundations: digest-bound pure helpers and bounded control flow; Core integrity, generic Target IR, and result projections; application-owned lawpack authoring; and the curated public Rust facade.
• observed — Modified behavior in ROADMAP.md: Added remaining work covering deterministic compiler/verifier/runtime package evidence, full Jedit application acceptance, Echo bridge acceptance, and independent facade package closure without publication. The roadmap states that Jedit #302 provides pure flat-text replacement reference evidence but does not complete persistent rope, authored graph effects, admission, settled Tick, or fresh-engine recovery; package acceptance alone does not establish stateful execution.
• observed — Modified behavior in ROADMAP.md: Added tracking for the separate Echo #693 complete-lawpack-closure dependency and closed Edict #203 pure-helper call-graph follow-up. GitHub-state comparison is planned, not enforced; runtime execution, admission, registry publication, and release tagging still require separate evidence and decisions.

Pre-merge checks: 3 · 2

Failed checks: 2 warnings

Check name	Status	Explanation	Resolution
Linked Issues check		Issue #187 requires two coding outcomes: update the frontier and add an automated check that binds the named frontier milestone to GitHub state. ROADMAP.md implements the first outcome. It explicitl…	Add the automated frontier-state check required by #187. Make the check validate the named milestone against GitHub state and add automated coverage for the relevant pass and failure cases. Then rerun the applicable validation.
Out of Scope Changes check		The ROADMAP.md frontier correction is in scope for #187. The two source-reference changes in docs/topics/public-rust-api/test-plan.md move PUBRUST-REQ-002 and PUBRUST-REQ-003 from #189 to #204, bu…	Remove the unrelated docs/topics/public-rust-api/test-plan.md reference changes from this PR, or submit them under the public Rust API planning work.

Passed checks: 3 passed

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Title check		The title clearly and concisely describes the documentation change: reconciling the bounded application build frontier.
Description check		The description directly explains the roadmap updates, package-closure references, scope, validation, and relationship to issue #187.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Full details: Linked Issues check

Explanation

Issue #187 requires two coding outcomes: update the frontier and add an automated check that binds the named frontier milestone to GitHub state. ROADMAP.md implements the first outcome. It explicitly states that automated comparison is only planned in #205 and that this correction does not provide enforcement. The required check and its test coverage are absent from this PR.

Resolution

Add the automated frontier-state check required by #187. Make the check validate the named milestone against GitHub state and add automated coverage for the relevant pass and failure cases. Then rerun the applicable validation.

Full details: Out of Scope Changes check

Explanation

The ROADMAP.md frontier correction is in scope for #187. The two source-reference changes in docs/topics/public-rust-api/test-plan.md move PUBRUST-REQ-002 and PUBRUST-REQ-003 from #189 to #204, but #187 concerns stale frontier and milestone-state validation. The linked issue does not require public Rust API ownership changes, and the PR provides no direct dependency that makes these edits necessary.

Resolution

Remove the unrelated docs/topics/public-rust-api/test-plan.md reference changes from this PR, or submit them under the public Rust API planning work.

• Fix all pre-merge checks with AI

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A frontier shifts; the roadmap turns
Foundations listed, evidence in view
Jedit and Echo work remain
Package closure waits its proof
Two issue references now align}

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