chore(docs): centralize open follow-ups and remove historical documentation

- add a single open-items tracker for active and optional backlog work
- remove historical-only docs and update references to canonical docs
- eliminate milestone/rollout wording (P1/P2/P7) across docs
- simplify architecture doc to current-state pipeline only
- replace deterministic-output migration wording with current compatibility guidance
- normalize worker/check-modules doc wording to current behavior

Author: KristjanESPERANTO

docs/CONTRIBUTING.md

@@ -78,7 +78,7 @@ For focused manual runs, point the pipeline at a small local wiki snapshot inste
 
 For regression testing, prefer the curated fixtures (`node --run fixtures:generate`, `node --run test:fixtures`, `node --run golden:check`) over ad-hoc subsets.
 
-## Release validation (Phase 4 rollout)
+## Release validation
 
 As of September 2025, schema validation is part of the release gate. After you regenerate the website data, run:
 
@@ -222,7 +222,8 @@ Golden artifacts are reference outputs stored in `fixtures/golden/` that serve a
 - [`docs/architecture.md`](architecture.md) – current vs. target pipeline topology.
 - [`docs/pipeline/orchestrator-cli-reference.md`](pipeline/orchestrator-cli-reference.md) – command reference for partial runs, diagnostics, and logs.
 - [`fixtures/README.md`](../fixtures/README.md) – curated dataset and validation troubleshooting.
-- [`docs/pipeline/shared-defs-scope.md`](pipeline/shared-defs-scope.md) – plan for consolidating shared JSON Schema `$defs` (task P1.6).
+- [`docs/pipeline/orchestrator-cli-reference.md`](pipeline/orchestrator-cli-reference.md) – current CLI and schema validation flow.
+- [`docs/open-items.md`](open-items.md) – central list of active cross-doc follow-up work.
 
 ### Troubleshooting
 

docs/architecture.md

@@ -1,6 +1,6 @@
 # Pipeline Architecture
 
-Visibility into the automation that builds and publishes the third-party module catalogue helps contributors reason about changes and spot failure points early. This document summarizes the current canonical pipeline, the legacy state we migrated from, and the parts of the broader architecture that are still future-facing.
+Visibility into the automation that builds and publishes the third-party module catalogue helps contributors reason about changes and spot failure points early. This document summarizes the current canonical pipeline and the parts of the broader architecture that are still future-facing.
 
 ## Current State (March 2026)
 
@@ -68,71 +68,9 @@ The pipeline implements intelligent caching and skip logic to avoid redundant wo
 
 ---
 
-## Legacy Workflow Snapshot (pre-September 2025)
+### Follow-Up Tracking
 
-```mermaid
-flowchart TB
-  subgraph Stage 1: Create Module List
-    wiki[("MagicMirror wiki table")] --> createLegacy{{Create module list<br>Node.js}}
-    createLegacy --> stage1Legacy["legacy stage-1 snapshot"]
-  end
-
-  subgraph Stage 2: Update Repository Data
-    stage1Legacy --> updateLegacy{{Update repository data<br>Node.js}}
-    updateLegacy --> cacheLegacy[("gitHubData.json cache")]
-    updateLegacy --> stage2Legacy["legacy stage-2 snapshot"]
-  end
-
-  subgraph Stage 3: Get Modules
-    stage2Legacy --> getLegacy{{Fetch repos<br>Python}}
-    getLegacy --> clonesLegacy[("modules/<br>modules_temp/")]
-    getLegacy --> stage3Legacy["legacy stage-3 snapshot"]
-  end
-
-  subgraph Stage 4: Expand Module List
-    stage3Legacy --> expandLegacy{{Enrich metadata<br>Node.js}}
-    expandLegacy --> imagesLegacy[("website/images/")]
-    expandLegacy --> stage4Legacy["legacy stage-4 snapshot"]
-  end
-
-  subgraph Stage 5: Check Modules JS
-    stage4Legacy --> checkjsLegacy{{Static checks<br>Node.js}}
-    checkjsLegacy --> stage5Legacy["legacy Stage-5 snapshot"]
-  end
-
-  subgraph Stage 6: Check Modules
-    stage5Legacy --> checkLegacy{{Deep analysis<br>Python}}
-    checkLegacy --> outputsLegacy[("modules.json<br>modules.min.json<br>stats.json<br>result.md")]
-  end
-
-  note1[["Mixed runtime: Python + Node.js"]]
-  note2[["No orchestrator: manual script execution"]]
-  note3[["6 sequential stages"]]
-```
-
-This legacy diagram captures the pre-orchestrator, mixed-runtime pipeline. Key issues that motivated the modernization:
-
-- Mixed Python + Node.js runtime made maintenance difficult
-- No orchestrator: manual script execution
-- No incremental updates: full run required every time
-- OOM risk with 1300+ modules loaded into memory
-- 6 sequential stages with 6 intermediate JSON files
-
-### Comparison: Legacy vs. Current Flow
-
-| Aspect             | Legacy (6 stages)         | Current flow (Mar 2026)                                                                                  |
-| ------------------ | ------------------------- | -------------------------------------------------------------------------------------------------------- |
-| Runtime            | Python + Node.js          | Node.js with TypeScript-based deep checks                                                                |
-| Execution          | Sequential manual scripts | Orchestrated 4-stage pipeline with in-process handoff                                                    |
-| Incremental        | ❌ No                     | Partial: metadata cache + clone reuse                                                                    |
-| Memory             | Unbounded                 | Batch-/worker-bounded                                                                                    |
-| Intermediate files | 6                         | none; only published outputs are written (`modules.json`, `modules.min.json`, `stats.json`, `result.md`) |
-
-### Remaining Gaps
-
-1. Reintegrate worker-compatible `moduleCache.json` handling under P7.6.
-2. Record before/after repeated-run performance metrics once cache writes are back in place.
-3. Keep the published contract (`modules.json`, `modules.min.json`, `stats.json`, `result.md`) stable while worker caching evolves.
+Open follow-up work is tracked centrally in [Open Items](open-items.md).
 
 No persisted intermediate stage boundary remains. Stage handoffs are fully in-memory.
 

docs/deterministic-outputs.md

@@ -153,41 +153,16 @@ No hashing required - the module identifier itself is already unique and determi
 - **Filename Generation**: Instant string concatenation
 - **Overall**: No measurable impact on pipeline runtime
 
-## Migration Notes
+## Compatibility Note
 
-### Existing Screenshots
+Some older snapshots in the repository may still contain pre-standardized screenshot filenames (for example, names derived from source paths). The current canonical output uses the deterministic `<moduleName>---<maintainer>.<extension>` format.
 
-When this feature was introduced, existing screenshots had filenames like:
+Downstream consumers should always read screenshot paths from `modules.json` rather than hard-coding file names.
 
-```text
-MMM-Weather---example---screenshot.jpg
-```
-
-After the change, new screenshots use:
-
-```text
-MMM-Weather---example.jpg
-```
-
-**Migration Strategy**:
-
-1. Old screenshots remain in place (not deleted)
-2. New pipeline runs generate hash-based filenames
-3. Gradual cleanup of old files as modules are re-processed
-
-**Breaking Change**: Modules linking directly to screenshot URLs will need updates. This is considered acceptable because:
-
-- Screenshot URLs should come from `modules.json`, not hard-coded
-- The migration improves long-term maintainability
-- Old files persist during transition
-
-## Related Tasks
-
-- **P3.4**: Ensure deterministic outputs (sorted keys, simple deterministic image names) ✅ Completed Nov 2025
+## Status
 
-## Future Improvements
+Deterministic output safeguards (sorted keys and deterministic image naming) are part of the current pipeline behavior.
 
-Potential enhancements (not currently planned):
+## Follow-Up Tracking
 
-1. **Canonical JSON**: Use RFC 8785 canonical JSON for cryptographic verification
-2. **Reproducible Timestamps**: Strip or normalize timestamps in metadata
+Potential deterministic-output enhancements are tracked centrally in [Open Items](open-items.md) under "Backlog (Optional)".