Next Steps
Current implementation evidence: docs/release.html, docs/release-compat.html,
docs/documentation-impact-review.html, docs/public-site-release-checklist.html,
and docs/roadmap.html.
Keep Learning
At this point you have seen the language shape, imports, capabilities,
packages, tests, runtime boundaries, app surfaces, diagnostics, and release
discipline.
Use these pages when you need exact answers:
Work Safely
Start with bounded checks while editing:
make public-site-link-check
make documentation-impact-check
make adr-rfc-check
Use broad release, self-host, runtime, browser, deployment, or all-library gates
only when that is the task.
Keep Docs Current
When behavior changes, update every affected learning page, reference page,
release note, support matrix, package page, and generated artifact in the same
change.
If no documentation changed, the ADR/RFC documentation impact review must say
why no documentation update was required.
Ship With Evidence
Before calling work production-ready, make sure the implementation, tests,
release artifacts, public docs, support matrices, and ADR/RFC records all agree.
The active full parity plan is Roadmap.