From 9b001a33a5eb10df55a53abc6b7b09d190e54180 Mon Sep 17 00:00:00 2001 From: cflmy Date: Fri, 20 Nov 2026 14:00:20 +0800 Subject: [PATCH] docs: fix relative links after status archival --- COMPATIBILITY.md | 2 +- docs/history/STATUS-M0.5-snapshot.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/COMPATIBILITY.md b/COMPATIBILITY.md index 155ac00..37ef301 100644 --- a/COMPATIBILITY.md +++ b/COMPATIBILITY.md @@ -49,7 +49,7 @@ reproduce the Windows checkout byte behavior. - `strict` additionally requires a kernel/environment that permits user, mount, PID and network namespaces, plus delegated cgroups. The current container does not, so strict is refused. See - [`docs/security-gate.md`](security-gate.md). + [`docs/security-gate.md`](docs/security-gate.md). ## Explicitly unsupported in this candidate diff --git a/docs/history/STATUS-M0.5-snapshot.md b/docs/history/STATUS-M0.5-snapshot.md index 3e3b812..e1e47a9 100644 --- a/docs/history/STATUS-M0.5-snapshot.md +++ b/docs/history/STATUS-M0.5-snapshot.md @@ -11,10 +11,10 @@ complete. > **M0.6 planning cross-reference (2026-11-20)**: this file is the M0.5 evidence > snapshot that the M0.6 audit was based on. Read -> [`docs/CORE_STABILIZATION_AND_ECOSYSTEM_GATE.md`](CORE_STABILIZATION_AND_ECOSYSTEM_GATE.md) +> [`docs/CORE_STABILIZATION_AND_ECOSYSTEM_GATE.md`](../CORE_STABILIZATION_AND_ECOSYSTEM_GATE.md) > (current-stage stabilization spec, baseline `0adebe4`), -> [`docs/EXTENSIBILITY_AUDIT.md`](EXTENSIBILITY_AUDIT.md) (issues E01–E16) and -> the proposed [`docs/NEXT_PHASE_IMPLEMENTATION.md`](NEXT_PHASE_IMPLEMENTATION.md) +> [`docs/EXTENSIBILITY_AUDIT.md`](../EXTENSIBILITY_AUDIT.md) (issues E01–E16) and +> the proposed [`docs/NEXT_PHASE_IMPLEMENTATION.md`](../NEXT_PHASE_IMPLEMENTATION.md) > alongside it. The stabilization spec supersedes the earlier plans on the > current baseline, gap list and G-A/G-B/G-C release gates; none of these plans > claims any gap below is fixed. Per audit item