docs(architecture): consolidate current state and history

This commit is contained in:
Marqdo Agent committed 2026-11-21 01:36:42 +08:00
1 parent 24c88bcc78
commit c2730ea445
10 files changed
+261 -22

No files matched your search

@@ -1,5 +1,11 @@
# Marqdo CLI 核心稳定化、协议冻结与独立生态准入实施规范
> **Historical review baseline (`0adebe4`, 2026-11-20).** The source review
> and CI facts here are a snapshot, not current state. The current overview is
> [`architecture/CURRENT.md`](architecture/CURRENT.md); executed status is in
> [`STATUS.md`](STATUS.md).
> **文档状态:Proposed / 可直接用作下一阶段工程实施基线**
> **源码审查基线:** [`cflmy/marqdo-cli@0adebe42f14d72a2a275564d03ff9558f197766e`](https://github.com/cflmy/marqdo-cli/commit/0adebe42f14d72a2a275564d03ff9558f197766e),`master`,2026-11-20。
> **验证来源:** 对上述提交的 GitHub 源码、规范、测试、CI workflow 和 [CI run #44671025763](https://github.com/cflmy/marqdo-cli/actions/runs/44671025763) 日志的静态审阅;**未在本文写作环境重新本地编译、运行测试或验证 OS 沙箱**。
@@ -1,5 +1,10 @@
# RFC-CM-0002:Marqdo 最小计算内核、标准库自举与系统能力迁移
> **Design input / Proposed.** This RFC records target semantics, not
> implemented behavior. The implemented first slice is described in
> [`architecture/CURRENT.md`](architecture/CURRENT.md).
> **状态**:Draft / 架构与迁移提案,未批准、未实施。所有代码均为目标语义草案,不能当作已运行示例。
> **日期**:2026-11-20
> **依赖与基线**:在《RFC-CM-0001:Marqdo 自主计算机器、可寻址内存与系统交互边界》之上细化,不代替其中的多内存区域与资源边界原则。
+5
View File
@@ -1,5 +1,10 @@
# RFC-CM-0001:Marqdo 自主计算机器、可寻址内存与系统交互边界
> **Design input / Proposed.** This RFC records target semantics, not
> implemented behavior. The implemented first slice is described in
> [`architecture/CURRENT.md`](architecture/CURRENT.md).
> **状态**:设计提案(Draft,未实施,未批准)
> **日期**:2026-11-20
> **建议归档路径**:`docs/architecture/RFC-CM-0001-compute-machine.md`
+7
View File
@@ -1,5 +1,12 @@
# Marqdo CLI M0.6(扩展性审计修订 v3)— 轻量核心、开放能力注册与独立生态实施规范
> **Historical planning input (M0.6).** This plan is superseded by
> [`STABLE_RELEASE_IMPLEMENTATION.md`](STABLE_RELEASE_IMPLEMENTATION.md)
> for next-phase work and is not current status. See
> [`architecture/CURRENT.md`](architecture/CURRENT.md) for the tree as it is today.
> Keep this file as design history; do not use it as an implementation claim.
> **文档性质**:面向没有参与任何历史讨论的开发者的独立架构决策、实施计划及验收契约。
> **建议仓库路径**:`docs/NEXT_PHASE_IMPLEMENTATION.md`
> **设计状态**:**Proposed / v3 破坏性架构纠偏**(需要维护者批准并通过验收;基于源码进行的扩展性审计要求:Tool Protocol、可调用函数、外部内核、ABI 导出、模块来源均消除不必要的硬编码扩展瓶颈)。
+6
View File
@@ -1,5 +1,11 @@
# Marqdo CLI:CI 收敛、语言边界回归与稳定发行实施规范
> **Historical baseline (`c9f01aa8`, 2026-11-20).** The CI SHA and run
> below are a snapshot. Refresh the remote SHA and CI evidence before use.
> The current overview is [`architecture/CURRENT.md`](architecture/CURRENT.md);
> executed status is in [`STATUS.md`](STATUS.md).
> **文档性质:** 可直接入库的执行规范 / Release Convergence Plan。供未阅读任何历史聊天的维护者、贡献者与 DeepSeek Harness 使用。
>
> **仓库:** `https://github.com/cflmy/marqdo-cli`;开发者的本地 Git 远端可能是 Gitee,不应混淆远端提交、GitHub 镜像与真实 CI 状态。
+30 -11
View File
@@ -1,22 +1,34 @@
# Marqdo Implementation Status
Snapshot: **2026-11-20**, workspace version `0.1.0`, no release tag.
Snapshot: **2026-11-21**, workspace version `0.1.0`, no release tag.
Current architecture overview:
[`architecture/CURRENT.md`](architecture/CURRENT.md).
Authoritative CI convergence plan:
[`NEXT_RELEASE_CI_CONVERGENCE.md`](NEXT_RELEASE_CI_CONVERGENCE.md).
[`NEXT_RELEASE_CI_CONVERGENCE.md`](NEXT_RELEASE_CI_CONVERGENCE.md) (historical
baseline at `c9f01aa8`; refresh before use).
Support matrix: [`../COMPATIBILITY.md`](../COMPATIBILITY.md).
This file records what was actually executed on the current tree. "Implemented"
does not mean "verified on every platform"; the evidence column says which
commands were run and where. The historical M0.5 snapshot is preserved at
commands were run and where. Do not copy a running status into another plan;
[`architecture/CURRENT.md`](architecture/CURRENT.md) is the single current
overview. The historical M0.5 snapshot is preserved at
[`history/STATUS-M0.5-snapshot.md`](history/STATUS-M0.5-snapshot.md) and must
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.
## 1. Remote baseline and current evidence
GitHub `master` is still `c9f01aa8fb127a2dcc125103ef794832984774ad`; the latest
public CI is run
[44692692318](https://github.com/cflmy/marqdo-cli/actions/runs/44692692318)
and is **red**:
The local baseline for this snapshot is
`24c88bcc78b1c705eb2319e7aaa8822a415eb01f` (2026-11-21). The later
documentation and test migration is recorded by its own commits; re-run the gate
before making a release claim.
The old GitHub `master` `c9f01aa8fb127a2dcc125103ef794832984774ad`
and public CI [run 44692692318](https://github.com/cflmy/marqdo-cli/actions/runs/44692692318)
are **historical (2026-11-20), not current**, and that run was red:
- Linux `fmt + clippy + test`: FAIL —
`strict_mode_enforces_isolation_or_refuses_closed` hit
@@ -26,11 +38,15 @@ and is **red**:
- Schema instance validation + consumers: PASS.
- Release candidate artifact: SKIPPED (upstream failure; tag/dispatch only).
The remote SHA must be refreshed from CI after a push; do not read `c9f01aa8`
as the current tree.
This checkout's private remote is `https://git.cflmy.cn/cflmy/marqdo-cli` with
Woodpecker CI at `https://ci.cflmy.cn` (`.woodpecker.yml`). The Linux Docker
pipeline runs fmt/clippy/test/release-build. GitHub native lanes, Windows/macOS
runners and a CI-attached strict VM runner are still unavailable; the G-C
evidence below remains local VM evidence.
pipeline runs fmt/clippy/test/release-build; the docs-consistency gate runs in
`cargo test --workspace`. GitHub native lanes, Windows/macOS runners and a
CI-attached strict VM runner are still unavailable; the G-C evidence below remains
local VM evidence.
Convergence code/security SHA: **`8af72620f12e2494a59830a23abb393768b610e9`**
(the following docs commit only adds this report and release material; code is
@@ -42,9 +58,12 @@ byte-identical).
cargo fmt --all -- --check PASS
cargo clippy --workspace --all-targets -- -D warnings PASS
cargo test --workspace --locked PASS
430 passed, 0 failed, 2 ignored; includes 7/7 Linux security tests
449 passed, 0 failed, 2 ignored; includes 7/7 Linux security tests
```
The documentation and test migration is local work; re-run this block after it
lands and update the count from the log rather than copying the number.
### G-C security lane (disposable Ubuntu 26.04 VM, ordinary user `dev`)
Source: `git archive 70d916d` extracted in the VM (not the dev container).
+151
View File
@@ -0,0 +1,151 @@
# Marqdo CLI — current architecture
Status: **current architecture overview**. This file summarises the tree as it
is today. It is not a release promise, does not reopen a frozen ADR, and does not
replace `spec/` or a recorded test log.
- Baseline: [`24c88bcc78b1c705eb2319e7aaa8822a415eb01f`](https://github.com/cflmy/marqdo-cli/commit/24c88bcc78b1c705eb2319e7aaa8822a415eb01f) (2026-11-21, before the documentation migration commit).
- Normative behavior: `spec/`; frozen decisions: `docs/adr/`; executed evidence: `docs/STATUS.md` and `docs/evidence/`.
- This is the **single current overview**. Do not add a second running "current state" file;
update this file, `docs/STATUS.md` and an evidence file together.
## 1. Four state dimensions
A claim is stated in exactly one of these dimensions. "Exists in the tree" is not
the same as "tested here", "published in the bundled stdlib" or "verified on a
platform".
| Dimension | Current state | Source |
|---|---|---|
| Implemented | Rust workspace `0.1.0`: Markdown/frontend/IR, tree-walk runtime, `Memory`, capability host, Tool/Analysis/Trace, Plugin ABI, Foreign kernels, bundled stdlib, CLI composition root | `Cargo.toml`, `crates/`, `stdlib/` |
| Tested locally | `cargo test --workspace --locked`: **449 passed, 0 failed, 2 ignored** on Linux x86_64 at the baseline | `docs/STATUS.md` §3 |
| Bundled stdlib released | In-repo bundle `marqdo-stdlib@0.1.0`, SHA-256 digest verified before loading; it is **not** an external registry package | `stdlib/stdlib.json`, `stdlib/README.md` |
| Multi-platform verified | Linux local gate is the only executed lane here; Windows/macOS native lanes are **UNVERIFIED**, and the GitHub security lane remains a **VM-only** gate | `docs/STATUS.md` §1, §4 |
## 2. Responsibility layers
```text
user .mq.md programs / agents / research workflows
|
stdlib/*.mq.md (versioned and digest-checked in this repository)
core / collections / text / encoding / data / math
io / console / stream / fs / net / process
memory / alloc + portable pure algorithms
|
language semantics: Markdown -> AST -> frontend -> IR
|
execution: Value / MemoryStore / evaluator / budgets
(computes; does not own stdout or file handles)
|
controlled platform API: open/read/write/close + non-streaming requests
capability / budget / audit / trace
stdio / file / tcp / OS adapters
explicitly registered providers (in-process / worker / C ABI)
|
OS / external services / devices
CLI is only the composition root: parse arguments, load the project,
assemble Host + Runtime, route output, exit with a status.
Callable Plugin / Foreign kernel / Tool Protocol are separate extension
categories; they do not enter the standard library or the language IR.
```
Layer rules:
1. The language core does not know `stdout`, a project directory, a TCP timeout
or a third-party plugin path.
2. The platform layer owns I/O, clocks, entropy, sockets and file handles. It must
not own JSON parsing, text formatting or memory allocation policy.
3. The stdlib is `.mq.md` and ships in this repository. New ordinary algorithms
go to `stdlib/` + tests + docs; they do not become Rust builtins.
4. The CLI selects inputs, resolves configuration, assembles the host and routes
human/machine output. It is not a semantic policy centre.
5. Callable Plugin and Resource Provider share one registry/authorization/audit
mechanism, but keep different capability types.
## 3. Dependency direction and public contracts
Current Rust dependency edges (documented, not proposed):
```text
marqdo-cli -> marqdo-runtime -> marqdo-host
marqdo-cli -> marqdo-package, marqdo-sandbox, marqdo-frontend, ...
marqdo-runtime -> marqdo-ir, marqdo-expression, marqdo-value
marqdo-host -> marqdo-plugin-abi, marqdo-foreign, marqdo-sandbox, marqdo-math
```
`marqdo-runtime -> marqdo-host` is the current direction. Do not add a second
execution backend or a `marqdo-stdlib` crate by implication. A future embedded
runtime or a second backend needs the thin `ExecutionPort` contract described in the
review RFC, not a new crate per provider.
| Public contract | API (`.mq.md`) | State | Tests |
|---|---|---|---|
| stdio stdin | `resource.open("stdio","stdin",["read"])`, `resource.read`, `resource.close`; one run-scoped cursor | implemented, read-only | `resource_streams`, `p2_closure`, `tests/conformance` |
| stdio stdout | `resource.open("stdio","stdout",["write"])`, `resource.write`, `resource.close`; separate output budget | implemented | `stdlib_bundle`, `print_routing`, `resource_streams` |
| stdio stderr | `resource.open("stdio","stderr",["write"])`; separate from stdout and CLI diagnostics | implemented | `resource_streams`, `stdlib_bundle` |
| project file read | `resource.open("file", path, ["read"])`; path/grant checked; bounded | implemented, project mode | `resource_streams`, `tests/e2e` |
| project file write | `resource.open("file", path, ["write"])`; buffers until `close`, never flush-on-drop | implemented, project mode | `resource_streams`, `resource_file_write` evidence |
| file metadata / directory / rename / remove / mkdir | not part of the current Resource contract | **not implemented**; needs a separate Resource Operation ADR | — |
| TCP | `resource.open("tcp", ip:port, ["read","write"])`; exact IP grant, 5 s timeout | implemented; no DNS/TLS/server socket/UDP | `tcp_endpoint`, `http_over_tcp` |
| HTTP/1.1 | `stdlib/net/http.mq.md`: status/header/chunked-byte parse, request build | implemented over an already-authorized TCP stream; not a DNS/TLS client | `stdlib_http`, `http_over_tcp` |
| print | bundled `io.mq.md`/`console.mq.md` through `resource.write`; legacy `HostOp::Print` removed | implemented (Compat-C) | `print_routing`, `stdlib_bundle` |
| strict mode | only the pure/Math execution path and the built-in stdout console channel; project/foreign/plugin/tool/trace/file/network grants are rejected | implemented L1; L2 not implemented | `tests/security`, `resource_streams` |
## 4. Extension path classification
| Extension path | Responsibility | State |
|---|---|---|
| Tool Protocol | external `marqdo` CLI tools, inspect/verify/IDE commands; versioned manifest and install/remove | implemented v1; not a standard-I/O replacement inside a user program |
| Callable Plugin ABI | native callable functions and controlled experimental acceleration | implemented v1 (native + worker); not an ordinary JSON/CSV formatter |
| Resource Provider | new resource kinds/devices/network/file endpoints | implemented v1 in-process, worker and trusted C ABI; not one provider per high-level algorithm |
| Foreign kernel | explicit cross-language compatibility for Python/Node one-shot execution | implemented; not a Marqdo implementation of common algorithms |
| Shared registry/policy/budget/audit/trace | package/adapter identity, descriptor/version checks, per-request grants, timeouts, error classes and trace metadata | housed inside `marqdo-host`; do not invent a shared binary ABI for function calls and resource streams |
## 5. Gap and closure backlog
This is the honest remaining work, ordered by the review RFC. It is not a claim
that a phase is complete.
| Priority | Gap | State |
|---|---|---|
| P0 | Stdlib release is a bundle in this repo; extraction is deferred (ADR-0039) | accepted, keep in repo |
| P0 | Documentation drift between `STATUS.md`, the architecture index and the evidence | being fixed by this migration and the docs gate |
| P1 | No `std:fs/file` product module; only a bundled first slice and Resource streams | open |
| P1 | No file stat/list/rename/remove/mkdir/append/seek capability | open; requires a Resource Operation ADR |
| P1 | JSON/CSV/UTF-8 decode remain mainly under `tests/conformance` | open as product stdlib API |
| P1 | `crates/cli/src/commands.rs` and `crates/marqdo-host/src/host.rs` still mix multiple responsibilities | open refactor, behavior-preserving |
| P2 | HTTP parsing is Unicode-codepoint oriented; a general byte body is not the only path | open; convert before a general network release |
| P2 | No DNS, TLS, listener or UDP provider | open |
| P2 | No `std:path`, `std:regex`, `std:datetime`, `std:env`, `std:process`, secure random or compression | open |
| P2 | Memory limits: 16 MiB per region, 64 MiB per run | current budget, not a product limit |
| P3 | No concurrency tasks, atomics or cancellable long-running scheduling | open; separate ADR |
| P3 | No native optimizer/JIT or columnar numeric backend | open; benchmark-first |
| P3 | Windows Native/Worker ABI is unsupported; macOS/Windows CI is unverified | open |
## 6. Documentation governance
1. There is one current overview (this file), one executed-state file
(`docs/STATUS.md`), frozen decisions in `docs/adr/`, and fact snapshots in
`docs/evidence/`. Do not copy a running status into several planning docs.
2. A design input (a proposed RFC or a historical planning doc) must say
**Proposed** or **Historical** in its own header. “Proposed” never means
“implemented”.
3. Every status row in `docs/STATUS.md` must name an executed command, a log or a
source path. Do not hand-edit a gate result without an evidence update.
4. Before committing a documentation change, run:
`cargo test -p marqdo-cli --test docs_consistency` and
`git diff --check`. A broken relative link or a stale “current” claim fails
the gate.
5. When behavior or status changes, update code + tests + `docs/STATUS.md` +
this file + an evidence file in the same change. A fixture/demo is not a
published stdlib API.
## 7. References
- [Architecture index](README.md) — RFC/ADR/evidence history.
- [Implementation status](../STATUS.md) — executed state and blockers.
- [Language/frontmatter blueprint](../DEVELOPMENT_BLUEPRINT.md) — design baseline; not current status.
- [Stable-release implementation plan](../STABLE_RELEASE_IMPLEMENTATION.md) — next-phase plan; not implemented behavior.
- [Compute-machine RFC-0001](../MARQDO_COMPUTE_MACHINE_RFC_0001.md) and [core/stdlib RFC-0002](../MARQDO_COMPUTE_CORE_STDLIB_MIGRATION_RFC_0002.md) — design input.
- [Architecture audit and refactor RFC](Marqdo_CLI_Latest_Architecture_Audit_and_Refactor_RFC.md) — review input for this migration.
+28 -11
View File
@@ -1,16 +1,24 @@
# Architecture RFCs: compute machine and stdlib migration
# Architecture RFCs: current state, decisions and design input
Status: **Draft RFCs, partially implemented**. This page is an index; the
normative RFC text stays at its reviewable path under `docs/`.
Status: **index**. The single current architecture overview is
[`CURRENT.md`](CURRENT.md). This page only indexes frozen decisions, design
input and evidence. It is not a second running-status page.
| Document | Status | Implemented part |
- Current architecture and four state dimensions: [`CURRENT.md`](CURRENT.md).
- Executed status and open blockers: [`../STATUS.md`](../STATUS.md).
- Frozen behavior: [`../../spec/`](../../spec/); release gates: [`../security-gate.md`](../security-gate.md).
- Historical planning snapshots: [`../history/README.md`](../history/README.md).
## Design input RFCs (Proposed, not implemented behavior)
| Document | Status | What it is |
|---|---|---|
| [RFC-CM-0001: compute machine, addressable memory and system boundary](../MARQDO_COMPUTE_MACHINE_RFC_0001.md) | Draft / design input | R1 (P1): `Memory` value, `memory.new/size/grow`, byte read/write, Memory-index assignment, budgets, wire/host rejection. Implemented per [ADR-0022](../adr/0022-addressable-memory-and-place-assignment.md); see [STATUS §5](../STATUS.md). |
| [RFC-CM-0002: minimal core, stdlib self-hosting and system capability migration](../MARQDO_COMPUTE_CORE_STDLIB_MIGRATION_RFC_0002.md) | Draft / design input | P0/P1, a **partial P2**, and a **partial P3** first slice (ADR-0025/0026/0040: stdin read, separate stdout/stderr write, granted project-file read and buffered project-file write via `resource.*`; strict permits only the stdio stdout console channel; ADR-0027/0030/0031 Compat-C print via bundled stdlib, no legacy host formatter). P2: fixtures 48–50 (`.mq.md` bump allocator, u32 codec, linked list/traversal, failed-allocation atomicity), CM-A04 structure primitives for List/Map/Text/Table (ADR-0023, fixtures 51–54), and a `.mq.md` first-fit free-list allocator with block splitting, address-adjacent coalescing and `Result` maps (ADR-0024, fixture 55), plus a `Memory`-backed binary tree with recursive insert/in-order traversal (fixture 56), a `.mq.md` CSV row splitter (fixture 57), an open-addressing hash table with linear probing (fixture 58), a `.mq.md` UTF-8 encoder and validating decoder (`utf8.truncated`/`invalid_continuation`/`invalid_scalar`) (fixtures 59–60), a `Memory`-backed graph adjacency list (fixture 61), a recursive JSON parser/formatter for arrays, objects, strings with escapes, ints/floats/booleans/null and error Results (fixture 62), a `Memory`-backed stack bytecode VM with PUSH/ADD/MUL/JMP/JZ/HALT (fixture 63), big-endian 16/32/64-bit plus LEB128 integer codecs (fixture 64), a `.mq.md` table sort rebuilding the table without mutating the input (fixture 65), a table join built from `table.row/columns/cell` (fixture 67), and a quoted/escaped CSV row parser (fixture 68), table group (fixture 69) and an Int matrix multiply (fixture 70). The stdlib intentionally remains in this repository for now (ADR-0039); no separate external repo, network/generic providers, P4 physical storage migration, P5 providers or P6 performance work. |
| [Architecture audit and refactor RFC](Marqdo_CLI_Latest_Architecture_Audit_and_Refactor_RFC.md) | **Review input** | Responsibility convergence, stdio/file/stream correctness, CLI/Host split and the current migration order. It is not evidence that a phase is done. |
| [Compute machine RFC-0001](../MARQDO_COMPUTE_MACHINE_RFC_0001.md) | **Proposed** | Opaque `Memory`, addressable regions, wire/host rejection. |
| [Core and stdlib migration RFC-0002](../MARQDO_COMPUTE_CORE_STDLIB_MIGRATION_RFC_0002.md) | **Proposed** | Minimum core, `.mq.md` stdlib and system-capability migration. |
The RFCs are architecture constraints, not evidence that a feature exists. The
implementation status lives in `docs/STATUS.md`; frozen behavior is in
`spec/`; decisions are in `docs/adr/`.
The implemented first slices of these RFCs are recorded in `CURRENT.md` and
`../STATUS.md`; the RFC text itself never proves that code exists.
## Decisions already frozen
@@ -37,7 +45,15 @@ implementation status lives in `docs/STATUS.md`; frozen behavior is in
| CM-A09 C ABI provider worker binding v1 | [0038](../adr/0038-c-abi-provider-worker-binding.md) | Accepted (trusted helper) |
| Stdlib extraction deferral | [0039](../adr/0039-stdlib-extraction-intent.md) | Accepted (in-repo for now) |
| Stdio stdin/stderr plus stdlib stream/console APIs | [0040](../adr/0040-stdio-stdin-stderr-and-stdlib-streams.md) | Accepted (stdin read, separate stdout/stderr, product stdlib) |
| Table physical storage (T1/T2/T3), strict stdin/stderr/file/network resources | — | Not decided; do not implement by implication |
| Table physical storage (T1/T2/T3), strict stdin/stderr/file/network resources | — | **Not decided**; do not implement by implication |
## Evidence and status
- Executed test counts, platform lanes and release blockers live in
[`../STATUS.md`](../STATUS.md). Do not repeat them here.
- SHA-pinned fact snapshots live in [`../evidence/`](../evidence/).
- Superseded planning input lives in [`../history/`](../history/), and its
remaining files carry a **Historical** banner.
## What a future phase must not do
@@ -48,4 +64,5 @@ implementation status lives in `docs/STATUS.md`; frozen behavior is in
safety for user allocators;
* make `strict` accept an unverified provider by default;
* claim an RFC phase is complete without the closure and negative evidence its
phase gate requires.
phase gate requires;
* edit a gate result in `../STATUS.md` without an executed log or a source path.
+23
View File
@@ -0,0 +1,23 @@
# Historical snapshots
This directory holds plans, reviews and status snapshots that were true at a past
commit but are **not current state**. They remain for provenance and design
history; do not cite them as what the tree does now.
- [`STATUS-M0.5-snapshot.md`](STATUS-M0.5-snapshot.md) — M0.5 status snapshot.
- `../NEXT_PHASE_IMPLEMENTATION.md` — M0.6 plan, superseded by
`../STABLE_RELEASE_IMPLEMENTATION.md`; the file stays under `../docs/` so
existing links keep working and carries a Historical banner.
- `../CORE_STABILIZATION_AND_ECOSYSTEM_GATE.md` — review baseline
`0adebe4`, marked Historical in place.
- `../NEXT_RELEASE_CI_CONVERGENCE.md` — CI baseline `c9f01aa8`, marked
Historical in place.
- The top-level `../Marqdo_CLI_Latest_Architecture_Audit_and_Refactor_RFC.md`
was a byte-identical duplicate of
`../architecture/Marqdo_CLI_Latest_Architecture_Audit_and_Refactor_RFC.md`;
it was removed in the documentation migration. The canonical copy is the
architecture one.
The current architecture overview is
[`../architecture/CURRENT.md`](../architecture/CURRENT.md); executed status is
[`../STATUS.md`](../STATUS.md).