Broken links report¶
Phase 2 resolution (Category A cross-entity)¶
Phase 1.5 deferred 10 cross-entity links until Phase 2 entity sync. After sync:
| Deferred target | Phase 2 outcome |
|---|---|
meridian/last1-meridian/MERIDIAN_SPEC.md |
Resolved (wiki link) |
meridian/last1-meridian/MERIDIAN_EVAL_SPEC.md (×2) |
Resolved |
meridian/last1-meridian/MERIDIAN_M0_KICKOFF.md |
Resolved |
meridian/last1-meridian/MERIDIAN_TELEMETRY_CONTRACT.md |
Resolved |
angel/angel/ANGEL_DEPLOYMENT_PLAN.md |
Resolved |
Sovereign/SOVEREIGN_DEPLOYMENT_PLAN.md (×2) |
Plain text only (file not in synced repos) |
Category A resolved: 8 of 10 (2 Sovereign deployment plan references remain prose-only).
See ../PHASE2_SYNC_REPORT.md for repo list and file counts.
Phase 1.5 summary (LastVet internal)¶
| Metric | Count |
|---|---|
| Original unresolved (Phase 1) | 191 |
| Category A deferred to Phase 2 | 10 |
| Category B removed (missing files) | 67 |
| Category C fixed (path updates) | 77 |
| Category D removed/TODO (PDF/binary) | 31 |
| Category E removed (.github/.cursor) | 6 |
| Remaining after Phase 1.5 (Category A only) | 10 |
Phase 2 entity link triage (deferred to Phase 3)¶
Synced entity repos retain source-relative links (PDFs, scripts, website routes, .cursor/ paths). MkDocs validation.links.not_found is info until per-entity polish in Phase 3.
Notes¶
- Phase 1.5 enabled
strict: truefor LastVet-internal link cleanup. - Phase 2 adds cross-entity targets under
content/entities/{meridian,angel,...}. - Chat export files under
entities/lastvet/api/docs/misc/exports/are excluded from the build (Railway template variable syntax conflicts with macros plugin).