fragJulia
Changelog

2026-04-25 — Operations docs: stale-reference annotations on migrated files

Added inline 'Update 2026-04-25' annotations on plan.mdx, sprint-337-358-328.mdx, and launch-audit-2026-04-04.mdx to flag references that have changed since the docs were originally written. Annotation-only — no original content rewritten. Spot-check, not a full audit.

Operations docs: stale-reference annotations

PR #682 migrated three operations docs from the repo root into apps/docs/content/docs/operations/:

  • plan.mdx (was root PLAN.md)
  • sprint-337-358-328.mdx (was root SPRINT_337_358_328.md)
  • launch-audit-2026-04-04.mdx (was root LAUNCH-AUDIT-2026-04-04.md)

The migration kept original content verbatim (these are dated docs whose value is partly historical). The migration PR body flagged three categories of stale references that should be made explicit so a future reader doesn't act on outdated info.

This changelog entry covers a doc-polish pass that adds inline > **Update 2026-04-25:** ... annotations at the relevant locations. Original content was not rewritten — annotations are additions only.

What was annotated

Category A — plan.mdx proxy.ts → middleware.ts rename

  • Architecture Overview "Key files" line still says proxy.ts (middleware). Annotated to point to apps/web/middleware.ts.
  • Sprint 4 issue #64's file list mentions proxy.ts as an alternate; annotated.
  • Sprint 0 action plan step 1 ("delete next.config.mjs, consolidate into next.config.ts") is inverted — next.config.ts no longer exists, next.config.mjs is the active config. Annotated.

Category B — sprint-337-358-328.mdx Phase 0 status

Phase 0 had 5 unblocker issues. Verified status against current main:

IssueStateClosed atReason
#338closed2026-04-12completed
#328openstill in progress
#355closed2026-04-07completed
#356closed2026-04-18completed
#357closed2026-04-07not_planned (folded into pipeline)

Annotated the Phase 0 table with the full status snapshot, plus inline notes on the #338, #357, and #355/#356 sections that asserted them as critical blockers.

Category C — launch-audit-2026-04-04.mdx findings spot-check

Top-of-file status banner added warning that the audit was 2026-04-04 and unannotated findings should be treated as "state unverified since audit date."

Per-finding annotations added where the file path was clearly resolved on main:

  • Finding 1 (CRITICAL — proxy.ts not active as middleware): resolved — apps/web/middleware.ts exists, apps/web/proxy.ts does not.
  • Finding 2 (HIGH — simplify route uses file_path instead of storage_path): resolved by architecture change — route now reads ocr_confirmed_text from the row.
  • Finding 6 (MEDIUM — missing app/error.tsx): resolved — file exists with branded GlobalError.
  • Finding 8 (LOW — debug console.log in yoga/new): resolved — current handleSubmit no longer logs form data.
  • Finding 9 (LOW — protectedPrefixes gaps): partially superseded — /forschung is now a permanent 301 redirect to docs.fragjulia.de per apps/web/next.config.mjs. Status of /zeitstrahl, /arztbrief, /chat left as unverified.

Findings 3, 4, 5, 7, 10 were not annotated — they reference behaviors or env-var policies, not file paths that can be confirmed by content lookup. Readers should treat them as "state unverified".

Important caveat

This is a spot-check, not a full audit. If a finding was not annotated, that does not mean it is still current — it means the current state was not verified in this pass. For an authoritative picture of any of these docs, run a fresh review.

Reference

  • Migration PR: #682
  • Touched files:
    • apps/docs/content/docs/operations/plan.mdx
    • apps/docs/content/docs/operations/sprint-337-358-328.mdx
    • apps/docs/content/docs/operations/launch-audit-2026-04-04.mdx
    • apps/docs/content/docs/changelog/meta.json (added this entry to pages)

On this page