docs(status): record the landed RFC-LANG-0002 implementation

Update status, compatibility, changelog, README, architecture overview,
ADR status, migration guide, contributor/CI/security/release notes and
the per-file inventory from 'migration pending' to the verified state:

- language SHA ffd1cc9: fmt/clippy clean, workspace 501 passed / 0 failed
  / 2 ignored, stdlib digest regenerated and pack-verified
- green evidence report added; the prior intermediate evidence is marked
  superseded
- inventory regenerated: 1015 classified files, 0 pending
- explicit non-claims: Windows/macOS native lanes and the disposable-VM
  strict lane were not re-run at this SHA, so the release decision remains
  DO NOT RELEASE

Verified: cargo test -p marqdo-cli --test docs_consistency (4/4) and
git diff --check.
This commit is contained in:
cflmy committed 2026-11-21 12:31:38 +08:00
1 parent ffd1cc9862
commit bbeb1de768
24 files changed
+425 -342

No files matched your search

+7 -8
View File
@@ -26,14 +26,13 @@ build (depends on test):
Node.js 22 is required because the optional foreign-kernel tests use ES-module
syntax; Debian bookworm's Node 18 fails those tests.
> **Language-syntax migration note.** `cargo test --workspace` includes
> conformance fixtures that execute `.mq.md` source. The target language is
> [RFC-LANG-0002](architecture/RFC-LANG-0002-unified-semantics.md) while the
> Rust frontend is still being migrated, so those executable-source tests are
> **expected to be red** on a correct migration branch. Do not interpret that as
> a CI-configuration regression or "fix" it by restoring the old mapper or
> regenerating goldens; see [`STATUS.md`](STATUS.md) and
> [`migration/README.md`](migration/README.md). The pipeline definition itself
> **Language contract note.** `cargo test --workspace` includes conformance
> fixtures that execute `.mq.md` source under
> [RFC-LANG-0002](architecture/RFC-LANG-0002-unified-semantics.md). The
> implementation, stdlib digest and corpus are green at `ffd1cc9`; a red
> executable-source suite is a real regression, not an expected migration
> state. Do not "fix" it by restoring the old mapper or regenerating goldens;
> see [`STATUS.md`](STATUS.md). The pipeline definition itself
> (fmt/clippy/test/build, security lane, platform gaps) is unchanged.
## What this pipeline does not cover