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

+58 -46
View File
@@ -19,53 +19,66 @@ not be read as current status.
Status is generated from executed commands and logs; a gate row without a command,
log or source path is a defect, not a state.
## 0. Language migration in progress (RFC-LANG-0002)
## 0. Language migration completed (RFC-LANG-0002)
The repository adopted a **breaking, single-syntax** language contract:
The repository now has **one** language contract, implemented end to end:
[`architecture/RFC-LANG-0002-unified-semantics.md`](architecture/RFC-LANG-0002-unified-semantics.md)
and [ADR-0052](adr/0052-unified-markdown-semantics.md), with the normative
summary in [`../spec/mapping.md`](../spec/mapping.md) and
(accepted by [ADR-0052](adr/0052-unified-markdown-semantics.md)), with the
normative summary in [`../spec/mapping.md`](../spec/mapping.md) and
[`../spec/expression.ebnf`](../spec/expression.ebnf).
What changed in this migration:
Landed in three commits on `semantics-v2-refactor`:
* active docs/spec/READMEs and all repository examples were rewritten to the
new heading-mode + unified-payload + keyword syntax;
* test-case source text (`tests/conformance/semantics`, `tests/negative`,
`tests/negative/runtime`, `tests/negative/warnings`, Rust-embedded fixtures)
was rewritten to the same syntax and the new `sem.*` diagnostics;
* no V1/V2 switch, `--legacy` path or dual active spec was introduced.
| Step | Commit | Content |
|---|---|---|
| 1 | `4983542` | docs/spec/ADR/READMEs, historical banners, migration guide and inventory |
| 2 | `e029853` | frontend/IR/runtime implementation, `sem.*` diagnostics, migrated stdlib + digest, examples, fixtures and Rust-embedded sources |
| 3 | `ffd1cc9` | expression-owned payload statement grammar, extra negative/CLI coverage |
What did **not** change in this migration:
The breaking behaviour is:
* the Rust frontend migration is only partially present in this worktree:
heading-mode/Knowledge-unit plumbing has begun, but the executable mapping
(`map.rs`), statement parser and the bundled `stdlib/**/*.mq.md` still follow
pre-RFC behaviour;
* as a result, `cargo test --workspace --locked` is **expected to be red**: the
semantic/negative/CLI fixtures now feed the old frontend. The last green
workspace run (491 passed, 0 failed, 2 ignored at `8af7262`) is historical
evidence for the pre-migration tree, not for this worktree;
* no platform, security or protocol result should be inferred from this
documentation migration.
* H1–H6 headings declare `@exec`/`@knowledge`; unmarked headings inherit the
nearest ancestor and the document root is Knowledge;
* only an Exec H2 is callable; an H2 Knowledge unit and H3–H6 sections are not
functions, and a payload with no owning Exec H2 is `sem.exec_without_function`;
* `Strong`, `Emph` and inline `Code` are interchangeable one-statement carriers;
nested carriers and empty payloads are hard errors;
* `if`/`else`/`while`/`end`/`return`/`params` come from the payload and lower to
the existing `Branch`/`Loop`/`Return`/`Assign`/`Eval` IR; lists, block quotes
and paragraphs are presentation containers;
* control frames cannot cross a heading segment;
* `params(...)` is legal only as the first direct Exec H2 payload; without it the
existing free-variable inference applies and inferred signatures keep the
named-arguments-only rule;
* old syntax (`Strong` execute / `Emph` return / list branch/loop / quote call)
is **not** executable, and `marqdo_semantics`/`syntax` front-matter selectors
are rejected with `sem.unsupported_version_directive`.
Observed in this worktree
([evidence](evidence/2026-11-21-semantic-docs-migration.md)):
`cargo fmt --all -- --check` PASS; `cargo check --workspace --tests --locked`
PASS; `conformance_ast` 4/4 PASS; `docs_consistency` 4/4 PASS;
`conformance_semantics` and `negative` FAIL as expected against the pre-RFC
frontend. The migrated example lock digest was regenerated with the real CLI.
### Verification at `ffd1cc9` (Linux x86_64, Rust 1.100.0)
Remaining work, owners and status: [`migration/README.md`](migration/README.md)
and [`migration/semantic-rewrite-inventory.tsv`](migration/semantic-rewrite-inventory.tsv).
A release is blocked until the frontend, expression parser, stdlib, fixtures and
all gates in RFC-LANG-0002 §12 are green on the same commit. Do not mark this
section complete before that evidence exists.
```text
cargo fmt --all -- --check PASS
cargo clippy --workspace --all-targets -- -D warnings PASS
cargo test --workspace --locked --no-fail-fast PASS
501 passed, 0 failed, 2 ignored (62 green test targets)
python3 tools/pack-stdlib.py PASS (digest verified)
```
Full evidence: [`evidence/2026-11-21-semantics-v2-green.md`](evidence/2026-11-21-semantics-v2-green.md).
The intermediate "text migrated, implementation pending" record is kept as
[`evidence/2026-11-21-semantic-docs-migration.md`](evidence/2026-11-21-semantic-docs-migration.md)
and is superseded by the green gate.
**Not claimed:** Windows/macOS native lanes and the disposable-VM strict
security lane were not re-run at this SHA. Those remain `UNVERIFIED`; see §1,
§4 and [`../COMPATIBILITY.md`](../COMPATIBILITY.md). The release decision is
still **DO NOT RELEASE** until the platform/security evidence is attached to a
single remote SHA.
## 1. Remote baseline and current evidence
The local baseline for this snapshot is
`24c88bcc78b1c705eb2319e7aaa8822a415eb01f` (2026-11-21). The later
The local language baseline for this snapshot is
`ffd1cc9862f7fe6002b42f1210010c1f78671a95` (2026-11-21, semantics v2 implementation). The later
documentation and test migration is recorded by its own commits; re-run the gate
before making a release claim.
@@ -131,11 +144,11 @@ This is still a **local VM lane**, not a self-hosted GitHub Actions security URL
## 2. Work package status
> **Pre-RFC baseline warning.** Rows and numbers in this section describe work
> executed before the RFC-LANG-0002 syntax migration. The Markdown/AST and
> platform/security rows remain valid; language-source rows (fixtures, control
> mapping, semantic goldens) are historical and are expected red until the
> frontend migration lands. See §0.
> **Historical table note.** Most rows in this section record work executed
> before the RFC-LANG-0002 syntax migration. Language-source rows (fixtures,
> control mapping, semantic goldens) were re-verified after the rewrite at
> `ffd1cc9` (§0); platform/security rows keep their original evidence dates and
> are not refreshed by the language migration.
| # | Work package | State | Evidence |
|---|---|---|---|
@@ -144,8 +157,8 @@ This is still a **local VM lane**, not a self-hosted GitHub Actions security URL
| 2 | Cross-platform strict `cfg` | **Fixed locally; native CI UNVERIFIED** | `#[cfg]` dispatch + non-Linux regression test |
| 3 | Strict probe→launch race | **Fixed locally; GitHub Linux CI UNVERIFIED** | fail-closed CLI contract + probe-OK/launch-EAGAIN seam test |
| 4 | Parallel security matrix isolation | **Fixed** | unique paths + helper `OnceLock`; 7/7 in parallel workspace run |
| 5 | Markdown/power/control-flow corpus | **Pre-RFC evidence; test text migrated, execution pending** | 160 AST + 73 semantic + 45 compile-negative + 2 warning + 21 runtime-negative fixtures after migration; suites expected red |
| 6 | Condition header + source spans | **Historical (old syntax)** | condition headers were removed by RFC-LANG-0002; payload/source-span rules live in `spec/mapping.md` §3 |
| 5 | Markdown/power/control-flow corpus | **Green on semantics v2** | 160 AST + 73 semantic + 47 compile-negative + 2 warning + 21 runtime-negative fixtures; `conformance_ast`/`semantics`/`negative` pass |
| 6 | Payload/control source spans | **Green on semantics v2** | UTF-8 spans, control-expression offsets and heading boundaries covered by fixtures and CLI tests; old condition headers were removed |
| 7 | Independent Tool consumers | **Done locally** | `sample-view`/`sample-knowledge`/`sample-proof` E2E test |
| 8 | lock v3 reproducibility | **Implemented; tamper test added** | `package_env` PASS |
| 9 | Analysis/Trace/Tool/ABI/Foreign | **Implemented; supported-matrix bounded** | protocol tests, plugin/worker/foreign tests |
@@ -159,10 +172,9 @@ This is still a **local VM lane**, not a self-hosted GitHub Actions security URL
- Frozen Markdown profile `marqdo.md.v1` with 160 AST goldens and explicit
CRLF byte semantics (unchanged by the semantic rewrite).
- Native Rust interpreter (pre-RFC mapping) with 73 migrated semantic fixtures,
45 migrated compile-error fixtures, 2 warning fixtures and 21 runtime-error
fixtures; the executable suites are **expected red** until the frontend
migration lands, so these are not current PASS evidence.
- Native Rust interpreter with the unified semantics: 73 semantic fixtures,
47 compile-error fixtures, 2 warning fixtures and 21 runtime-error fixtures
all green at `ffd1cc9`; AST profile unchanged (160 goldens).
- Native `**` power is pinned end-to-end: right associativity, unary-minus
precedence, parentheses, float negative exponents, branch/loop conditions,
Strong+CodeSpan payloads, and inert prose/code fences.