From 73f5e8207753d85e7006f9955bd0e144c42c434a Mon Sep 17 00:00:00 2001
From: hkwuks <25031515+hkwuks@users.noreply.github.com>
Date: Sat, 31 Oct 2026 00:23:05 +0800
Subject: [PATCH] docs: archive 2026-10-29-schema-check

The task landed in PR #104 and its three Steps were already `done`; only
the archive never ran, so the directory sat under `TaskFlowDocs/` and the
Todo entry still read `in_progress` with a Next action asking for a
v2 re-approval that had already happened on 2026-10-29 20:50.

`hooks/task complete` moves the task directory to `achieved/`, reduces the
Todo entry to the five fields triage still needs, and sets both documents
to `completed`. No code changes: everything this task shipped is already
on `main` in ae4c60d.
---
 .../2026-10-29-schema-check/old/v1/prd.md             |  0
 .../2026-10-29-schema-check/old/v1/version.md         |  0
 .../{ => achieved}/2026-10-29-schema-check/plan.md    |  2 +-
 .../{ => achieved}/2026-10-29-schema-check/prd.md     |  2 +-
 TaskFlowDocs/todo.md                                  | 11 +++--------
 5 files changed, 5 insertions(+), 10 deletions(-)
 rename TaskFlowDocs/{ => achieved}/2026-10-29-schema-check/old/v1/prd.md (100%)
 rename TaskFlowDocs/{ => achieved}/2026-10-29-schema-check/old/v1/version.md (100%)
 rename TaskFlowDocs/{ => achieved}/2026-10-29-schema-check/plan.md (99%)
 rename TaskFlowDocs/{ => achieved}/2026-10-29-schema-check/prd.md (99%)

diff --git a/TaskFlowDocs/2026-10-29-schema-check/old/v1/prd.md b/TaskFlowDocs/achieved/2026-10-29-schema-check/old/v1/prd.md
similarity index 100%
rename from TaskFlowDocs/2026-10-29-schema-check/old/v1/prd.md
rename to TaskFlowDocs/achieved/2026-10-29-schema-check/old/v1/prd.md
diff --git a/TaskFlowDocs/2026-10-29-schema-check/old/v1/version.md b/TaskFlowDocs/achieved/2026-10-29-schema-check/old/v1/version.md
similarity index 100%
rename from TaskFlowDocs/2026-10-29-schema-check/old/v1/version.md
rename to TaskFlowDocs/achieved/2026-10-29-schema-check/old/v1/version.md
diff --git a/TaskFlowDocs/2026-10-29-schema-check/plan.md b/TaskFlowDocs/achieved/2026-10-29-schema-check/plan.md
similarity index 99%
rename from TaskFlowDocs/2026-10-29-schema-check/plan.md
rename to TaskFlowDocs/achieved/2026-10-29-schema-check/plan.md
index 8568a17..88a4517 100644
--- a/TaskFlowDocs/2026-10-29-schema-check/plan.md
+++ b/TaskFlowDocs/achieved/2026-10-29-schema-check/plan.md
@@ -1,6 +1,6 @@
 # Plan — 断言 manifest 的 `$schema` 声明
 > Task version: v2
-> Status: in_progress
+> Status: completed
 
 No spec required — small, self-contained task.
 
diff --git a/TaskFlowDocs/2026-10-29-schema-check/prd.md b/TaskFlowDocs/achieved/2026-10-29-schema-check/prd.md
similarity index 99%
rename from TaskFlowDocs/2026-10-29-schema-check/prd.md
rename to TaskFlowDocs/achieved/2026-10-29-schema-check/prd.md
index a0040c8..fa25b59 100644
--- a/TaskFlowDocs/2026-10-29-schema-check/prd.md
+++ b/TaskFlowDocs/achieved/2026-10-29-schema-check/prd.md
@@ -1,6 +1,6 @@
 # 断言插件 manifest 声明的 `$schema` 可用
 > Task version: v2
-> Status: in_progress
+> Status: completed
 
 ## Goal
 
diff --git a/TaskFlowDocs/todo.md b/TaskFlowDocs/todo.md
index 0ab751e..a03be7a 100644
--- a/TaskFlowDocs/todo.md
+++ b/TaskFlowDocs/todo.md
@@ -29,15 +29,10 @@ has an issue number or URL.
 ## Assert the $schema a plugin manifest declares, so a schema URL that stops resolv
 
 - ID: TF-20261029-218fdf
-- Status: in_progress
-- Priority: normal
-- Owner: Claude
-- Source: user request 2026-10-29 (TF-20260928-3910fb re-scoped)
-- Added: 2026-10-29
-- Updated: 2026-10-29
+- Status: done
 - Goal: Assert the $schema a plugin manifest declares, so a schema URL that stops resolving or a manifest that drops one fails a check instead of shipping
-- Task: `TaskFlowDocs/2026-10-29-schema-check/`
-- Next action: Re-approve v2: A1 now expects STATUS: pass, since the offline assertion cannot detect the two 404 URLs.
+- Task: `TaskFlowDocs/achieved/2026-10-29-schema-check/`
+- Next action: None — completed and archived.
 
 ## task approve requires the first [Plan] line to name exactly the capability relea