Skip to content

T-EC4B-site-corpus-high-volume-types

Status: closed/done · Impact: medium · Complexity: medium

Project the high-volume types — task and backlog — and measure the build against the recorded budget, closing D-0010’s open question with data. D-0010-deterministic-site-assembly §4, Migration Phase 6.

LocationRole today
docs/planning/tasks/Hundreds of entities, no site projection
docs/planning/backlog/Dozens of entities, no site projection

Task projects with a site_projection.ts override (Status / Impact / Complexity roster columns; depends_on rendered as links on child pages). Backlog ships generic. Both join the Planning nav group. Build time and Pagefind index size are measured before/after and recorded on this task; if the budget breaks, the designed mitigation (a child_pages: false projection flag rendering roster-only) is implemented here, not designed here.

  1. Task override: roster columns + depends_on links on child pages.
  2. Enable backlog via the generic projection.
  3. Measure: astro build wall-clock and index size at baseline and after; record both in the completion note.
  4. If over budget: implement child_pages: false and apply to the offending type.
  5. Tests: task-override fixtures, depends_on link resolution.
LocationKindChange
plugin/lib/model/entities/task/site_projection.tsnewOverride
plugin/lib/services/docs/site/projections.tsmodifyBacklog enablement; child_pages flag if triggered
plugin/lib/services/docs/tests/modifyOverride suites
  • AC-1: /planning/tasks/ roster shows Status/Impact/Complexity; task child pages link resolved depends_on targets.
  • AC-2: /planning/backlog/ renders via the generic projection.
  • AC-3: Build-time and index-size measurements recorded; budget verdict stated.
  • Pagination or client-side filtering of large rosters — future work if the measurement demands it.

Extracted from D-0010-deterministic-site-assembly Migration Phase 6.

T-I6WC-site-corpus-curated-types


← Back to Tasks