Roadmap
Implemented capability is kept apart from adoption evidence: a feature proven in CI is not proof that a reader uses it.
Available now
- Build-time page history from one git index per build: six git commands warm, seven cold, whatever the page count (ADR-0002).
- Semantic block ids on rendered pages, shared with the service (ADR-0003).
- The three review capabilities, proven end to end in a browser against a mock
GitLab on every pipeline: inline redline, changed since, anchored comments, plus
GitLab OAuth and the network failure states (
test/e2e/). - A Tailscale-only deployment configuration with a persistent QA environment (ADR-0008).
- Redline’s own dashboard rendering this knowledge base with its review tools (ADR-0007).
Adoption in progress
Stage 1, standalone. The dashboard and API on one origin at yqa.fio.sh,
QA at qa-yqa.fio.sh, proven against real GitLab. Completion means recorded
smoke and live-spec evidence in both environments, one real merge request shown
inline and one real comment attributed in GitLab. See the
experiment plan, batch B6.
Stage 2, YYZ. Deferred. YYZ’s pages come from kb-packages, which need
block ids (TD-002), history from their bundles (TD-003) and multi-project sites
(TD-004) before Redline can attach. The usage measurement
(scripts/experiment-report.js) belongs to this stage.
Next, in priority order
| Priority | Outcome | Acceptance evidence |
|---|---|---|
| 1 | The dashboard ships inside the image and is served on its own origin | Experiment plan T6.2 and T6.4 done; the image contains /app/site/index.html |
| 1 | Stage 1 deployed and proven | Experiment plan T6.7 evidence for QA and production |
| 1 | Verify rulesets active (TD-001) | prettier, eslint and tsc jobs green on the experiment branch |
| 2 | kb-package compatibility planned (TD-002 to TD-004) | An approved plan for Stage 2 |
| 3 | Release gate covers npm too (TD-007) | Candidates no longer tagged latest |
Decisions still needed
- Who owns the deployed service, and what availability readers can expect.
- Whether block ids for kb-packages belong in the harvester or the renderer (TD-002).