## What

Mints the three requirements W6 of SEAMLESS-UPDATES (#331) needs, all **unactivated** (`required_stages = []`). No code, no docs, no behavior: `traceable-reqs.toml` only.

W6 (#337 + #64 + #340) carried three requests and **zero** covering REQs — the same blocker that made W5 undispatchable until `REQ-BUNDLE-APPLY-MEMBERS` was minted. This unblocks the W6 dispatch.

## Why three new ids and not three re-tags

Each near-miss was read in full; all three are different surfaces.

| Request | Near-miss | Why it does not cover |
|---|---|---|
| #337 | `REQ-NOW-SIGNAL-UPDATES` | Already **satisfied** by the shipped row shape. The moved-subject row needs applied-at and the OLD version from the apply record (written by **both** the CLI and the daemon pump). New impl + new units ⇒ re-tagging would gate the change on nothing. |
| #64 | `REQ-TRUST-WARNING-OVERRIDE` | Governs the endpoint **trust-warning** advisory paragraph, elevation-gated, node-local. #64 is the **release trust anchor** read out of `identity/release-keys.json` and reported by `spt update status`. Shared noun, different claim. |
| #340 | `REQ-DOCS-CHANGELOG-PAGE` | That is the docs-**site** changelog page. Nothing covered per-adapter `[adapter] summary`/`changelog`, its render, or its served route. |

## Constraints carried into the REQ text

- **#337 is operator re-ruled (2026-09-24 08:20Z): no new notification surface, no ADR-0046 notif row.** The divulge lives inside the existing now-signal `<UPDATES>` block; `REQ-NOW-SIGNAL-UPDATES`'s seen-set-as-event-detector stays the only source for "something moved".
- #337 and #340 are coupled: the row's `changelog:` suffix appears only when the adapter declares one.
- #340 adds `pulldown-cmark` — a **new dependency**, to be justified in the delivering PR body, not here.
- #340's doc stage lands on `docs/MANIFEST.md` + the schema in the same commit as the parser (the `REQ-SHELL-HINTS` precedent: a manifest section no author can find reads as absent).

## Activation

All three stay `required_stages = []` per AGENTS.md rule 5. Each carries a comment naming the stages to set at W6 dispatch and why (`int` only where a real boundary is crossed — the served-route leg for #340).

## Evidence

- `traceable-reqs check` — exit 0, all three registered.
- Seed record: `.spt/preserved/331/w6-req-gap.md`.

Note for the reviewer: this diff is suite-inert (no test or build reads `traceable-reqs.toml`), but the change classifier's docs set is `.md`-only, so it classifies `code=true` and runs the full lane. Filed to the infra register rather than worked around here.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01SgutL1VJbbSwoa7NSsKuHp