docs(W4): stamp kind and status front matter on 104 live documents

Applies the document contract from
docs/plans/2026-08-20_stack-docs-flatten-and-alignment.md section 3, partially:
`kind` and `status` only. `parent` is deliberately held until the flatten in
section 4 lands, so that 127 documents do not have to be re-pointed by hand
when docs/fleet/NORTH_STAR.yaml moves to docs/NORTH_STAR.yaml.

Scope, measured on origin/next at 63069149:

  127 live docs   = all *.md under docs/ minus docs/archive/ minus docs/_old_structure/
  104 stamped     here
   19 held        operator judgement (plan section 9), worklist in the same PR
    3 held        the SUPERSEDED TASKS.md stamps, which cite the moving path
    1 untouched   docs/fleet/FLEET-DOCTRINE.md, already stamped in W1

Kinds applied: 54 guide, 34 record, 9 spec, 6 tracking, 1 projection.
Every row carries a confidence and a one-line rationale in the worklist.

Two collisions with the existing state, both flagged rather than resolved:

1. docs/README.md:150-160 already documents a front-matter convention
   (title/type/audience/status/source_of_truth) with its own allowed values.
   It is applied to 4 of 127 files. Its `status` vocabulary is
   current|draft|deprecated|historical; the new contract's is active|superseded-by.
   The key collides. This commit lets the new contract win and rewrites
   `status: current` to `status: active` on those 4 files, keeping their other
   legacy keys untouched. No code reads any of them: `git grep source_of_truth`
   outside docs/ returns nothing. docs/README.md still prescribes the old
   convention and is an operator row, so it is not edited here.

2. Two of the plan's 20 operator rows are YAML files, not markdown
   (docs/fleet/examples/roster-v2.yaml, docs/openapi-tess.yaml), and the
   contract's front-matter form has no defined meaning for a .yaml document.
   That gap also applies to docs/fleet/NORTH_STAR.yaml, the source of truth
   itself. Raised in the worklist.

A third row from the plan, docs/fleet/north-star.md, no longer exists: W1
renamed it to docs/fleet/FLEET-DOCTRINE.md.

Verification: 104/104 parse with the expected kind and status in front matter;
the check was shown to reject a wrong kind before it was trusted. The diff
removes 4 lines total, all of them `status: current`.

docs/reports/README.md

@@ -1,3 +1,8 @@
+---
+kind: guide
+status: active
+---
+
 # Documentation Reports
 
 > **Status:** Current evidence index. Reports record reviews, tests, audits, and deferred findings; they are not requirements or operational instructions by themselves.

docs/reports/code-review/756-code-review.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # Independent Code Review — #756 Official Discord Channel Plugin
 
 **Verdict: APPROVE**

docs/reports/code-review/gateway-security-20260313.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # Code Review Report — Gateway Security Hardening
 
 ## Scope Reviewed

docs/reports/compaction-refresh/830-documentation-checklist.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # #830 Documentation Completion Checklist
 
 ## Required artifacts

docs/reports/deferred/758-fleet-config-deferrals.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # FCM-M5-001 Fleet Documentation Deferrals and Holds
 
 **Issue:** #758 · **Branch:** `docs/758-fleet-config-operator-docs`

docs/reports/documentation/2026-08-10-docs-catalog-audit.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # Mosaic Stack Documentation Catalog and Truth Audit
 
 > **Status:** First-pass static audit — 2026-08-10

docs/reports/documentation/756-discord-plugin-checklist.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # Documentation Completion Checklist — #756 Official Discord plugin
 
 ## Required artifacts

docs/reports/documentation/758-fleet-config-ia-closure.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # FCM-M5-001 Fleet Documentation IA Closure Evidence
 
 **Issue:** #758 · **Task:** FCM-M5-001

docs/reports/documentation/AUDIT-2026-02-17-framework-consistency.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # Mosaic Framework Consistency Audit
 
 Date: 2026-02-17

docs/reports/native-kanban-sot/canon-final-rereview-go.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 VERDICT: GO
 
 # Native Kanban/SOT canon independent re-review 2

docs/reports/native-kanban-sot/canon-initial-review-no-go.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # Independent Review — Native Kanban/SOT Canon
 
 **Reviewer:** `enhance-sol` (independent of author `planner-sol`)

docs/reports/native-kanban-sot/kbn-101-contract-security-review-82ce325.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # KBN-101 contract independent security/architecture review
 
 **Verdict: REQUEST CHANGES**

docs/reports/native-kanban-sot/ultron-final-go.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # #751 Native Kanban/SOT canonical publication — Ultron final gate
 
 **Verdict: GO** — zero BLOCKER/HIGH findings.

docs/reports/qa/gateway-security-20260313.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # QA Report — Gateway Security Hardening
 
 ## Scope

docs/reports/qa/p8-003-performance-optimization.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # Performance Optimization — P8-003
 
 **Branch:** `feat/p8-003-performance`  

docs/reports/quality/1099-pipefail-sweep.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # #1099 pipefail + early-exit sweep
 
 Baseline: `df4c591ab42aa1ae62c12935fdc0e772684864a0`

docs/reports/security/756-security-review.md

@@ -1,3 +1,8 @@
+---
+kind: record
+status: active
+---
+
 # Security Review — Issue #756
 
 **Scope:** final current uncommitted Discord plugin, shared channel contract, gateway ingress, AgentService, and plugin registration delta