Remove reset watch and historical plans

README.md

@@ -334,7 +334,6 @@ The tracked workspace currently keeps:
 - `docs/decisions/` as the durable design-rationale lane
 - `docs/research/` as machine-authored research artifacts used by shipped research
   tooling
-- `docs/plans/` as historical saved plan artifacts from the static-site bootstrap
 - `dev/` as local development helpers outside `dev/skills/`, such as the operator
   dashboard mock server
 - `assets/` as generated Decodex App icon source notes, Icon Composer foreground,

dev/skills/README.md

@@ -23,8 +23,6 @@ content or follow-up work:
    `decision.worthiness = "publish"` or explicit operator handoffs that name checked
    Radar artifacts, then write a low-frequency
    `social_post/v1` publication, block, skip, or failure record for `@decodexspace`.
-6. `rate-limit-reset-watch`: review today's `@thsottiaux` X posts with AI semantic
-   judgment and refresh the homepage `reset_status/v1` artifact.
 
 Use only the skills needed for the current artifact. Do not publish a social post just
 because a signal exists.
@@ -63,6 +61,6 @@ release metadata, compare metadata, and caveats create real reader value.
 Checked-in contracts for this workflow are `upstream_review_queue/v1`,
 `upstream_review/v1`, `github_change_bundle/v1`, `analysis_draft`, `signal_entry/v1`,
 `upstream_impact/v1`, `release_delta/v1`, `social_candidate/v1`, `social_post/v1`, and
-`reset_status/v1`. The triage, code-analysis, release-analysis, and reset-watch skills
-are reasoning passes unless their conclusions are promoted into one of those
+their supporting generated artifacts. The triage, code-analysis, and release-analysis
+skills are reasoning passes unless their conclusions are promoted into one of those
 contracts.

docs/index.md

@@ -23,8 +23,6 @@ The split below is by question type, not by human-versus-agent audience.
   - `docs/reference/index.md` when the question is "how is it currently organized or
     implemented?"
   - `docs/decisions/index.md` when the question is "why was it designed this way?"
-- Use `docs/plans/` only when a planning tool or historical execution workflow
-  explicitly points to a saved plan artifact there.
 
 ## Routing matrix
 
@@ -73,8 +71,6 @@ The split below is by question type, not by human-versus-agent audience.
 - Need repository execution defaults or tracker-state policy -> registered project
   `WORKFLOW.md`
 - Need repo task names or automation entrypoints -> `Makefile.toml`
-- Need historical saved execution plans from the original static-site bootstrap ->
-  `docs/plans/`
 
 ## Retrieval rules
 
@@ -93,7 +89,6 @@ The split below is by question type, not by human-versus-agent audience.
 - Start each document with a short routing header that says what the document is for,
   when to read it, and what it does not cover.
 - Keep links explicit and stable.
-- Treat `docs/research/` and `docs/plans/` as supporting or historical evidence, not as
-  primary authority lanes.
+- Treat `docs/research/` as supporting evidence, not as a primary authority lane.
 - Treat research output as latent until accepted or promoted through the loop-runtime
   contract in `docs/spec/loop-runtime.md`.