Production Version Gap Report (2026-04-06)
Production Version Gap Report — 2026-04-06
Section titled “Production Version Gap Report — 2026-04-06”This report inventories the current repository state and compares:
- Production-tracked version metadata (
version.json) - Roadmap-reported platform state (
ROADMAP.md) - Documented release/change history (
docs/CHANGELOG.md)
Date of analysis: 2026-04-06 (UTC).
Current State Snapshot
Section titled “Current State Snapshot”| Source | Value | Date in File | Notes |
|---|---|---|---|
version.json | version: 1.0.0, phase: GA | lastUpdated: 2026-04-04T01:10:00Z | Production metadata points to stable 1.0.0 with professional platform infra flagged separately (1.2.0-phase1). |
ROADMAP.md | Current version banner 1.0.0 (Stable) | Released 2026-03-22, last updated 2026-03-31 | Mixed milestone narratives include 1.0.0 GA and in-progress 1.2.0 milestone text. |
docs/CHANGELOG.md | Latest stable release section 1.0.0 + additional 1.2.0-phase1 | 1.2.0-phase1 dated 2026-03-28; unreleased contains many post-release entries | Changelog correctly captures post-1.0.0 changes but blends unreleased operational notes and historical release notes. |
Production vs Documentation Gap Analysis
Section titled “Production vs Documentation Gap Analysis”1) Version labeling gap
Section titled “1) Version labeling gap”- Production target remains
1.0.0, withversion.jsonexplicitly indicating GA and deployment URLhttps://trystpilot.xyz. - Documentation describes substantial
1.2.0-phase1work as merged and in progress, but this is not represented as the deployed production version.
Gap impact: Readers can misinterpret feature completeness and availability in production.
2) Date freshness gap
Section titled “2) Date freshness gap”version.jsonupdated on 2026-04-04.ROADMAP.mdbanner last updated on 2026-03-31.docs/CHANGELOG.mdhas entries through unreleased state but no explicit “production deployed on” reconciliation entry after 2026-04-04.
Gap impact: Operations and product docs are out of sync by multiple days and lack explicit deployment reconciliation.
3) Status claims vs known breakage gap
Section titled “3) Status claims vs known breakage gap”Known active breakages called out by current triage context:
- GitHub authentication issues
- Telegram authentication issues
- Admin password flow issues
/statusendpoint reliability issues
Current public docs still include complete/production-ready language in multiple places for auth and status.
Gap impact: High risk of false confidence during incident response and sprint prioritization.
Top 3 Priorities (ordered)
Section titled “Top 3 Priorities (ordered)”-
P0 — Auth reliability stabilization
Validate and fix GitHub OAuth, Telegram callback/session flow, and admin password path; publish a single truth table of current auth states. -
P0 —
/api/statustruthfulness and uptime
Ensure endpoint returns stable health data and clearly distinguishes degraded dependencies from total failure. -
P1 — Documentation information architecture separation
Enforce strict boundary betweendocs.trystpilot.xyz(runbooks/reference) anddesign.trystpilot.xyz(design system, architecture diagrams, UX assets).
Blockers / Constraints
Section titled “Blockers / Constraints”- No production runtime logs in-repo for direct root-cause confirmation.
- Mixed historical status claims in legacy docs make machine parsing unreliable.
- Two-site doc architecture has overlapping UI/UX content ownership.
- Some roadmap/changelog sections are narrative-heavy without explicit deploy status fields.
Immediate Next Steps
Section titled “Immediate Next Steps”- Create explicit docs-vs-design ownership map and cross-link policy.
- Remove UI design system ownership from docs-site navigation.
- Add boundary pages in both sites explaining where content belongs.
- Add a release hygiene checklist requiring synchronization of
version.json, roadmap banner date, and changelog deploy note.