Project State, Version Control, and Blockers (2026-04-06)

Project State, Version Control, and Blockers — 2026-04-06

Sources Reviewed

• version.json (production metadata)
• ROADMAP.md (delivery and milestone narrative)
• docs/CHANGELOG.md (release and implementation chronology)
• docs/EXECUTION_THREADS_2026-04-06.md (prior workstream plan)

Current Version Control Snapshot

Source	Current Value	Date	Interpretation
version.json	1.0.0, phase GA	2026-04-04T01:10:00Z	Production source-of-truth remains 1.0.0
ROADMAP.md banner	1.0.0 (Stable)	Released 2026-03-22; updated 2026-03-31	Product roadmap not fully reconciled with latest production metadata date
docs/CHANGELOG.md	1.0.0 + 1.2.0-phase1 narrative	Through late March 2026 entries	Mixed released + in-progress language requires clearer status labels

Primary Blockers

1. Authentication reliability gaps (P0)

   • GitHub OAuth is reported broken in current triage context.
   • Telegram auth/session callback is reported broken.
   • Admin password authentication path is reported broken.

2. Status endpoint truthfulness (P0)

   • /api/status reported as broken or unreliable.
   • Current docs overstate status reliability vs active triage reports.

3. Documentation ownership/version governance drift (P1)

   • Confusion over docs site vs design site ownership boundaries.
   • Discovery UX artifacts are incomplete/outdated (relationship variants, discovery channels, user intent maps, ASCII frame coverage).

4. Validation environment constraints

   • Production logs/secrets are not available in this repository context for full runtime root-cause confirmation.

Current Steps (Execution-Ready)

Step 1 — Stabilize auth tracks (P0)

• Build and publish provider-by-provider auth truth table.
• Validate code paths and environment expectations for GitHub, Telegram, and admin-password auth.
• Mark each provider as working, degraded, or broken in one canonical doc artifact.

Step 2 — Repair and harden /api/status (P0)

• Verify endpoint behavior for healthy vs degraded dependencies.
• Ensure clear response semantics when upstream services timeout or env vars are missing.
• Add tests/checks to prevent regressions.

Step 3 — Enforce docs/design separation + version governance (P1)

• Add ownership matrix with file-identification and version labels.
• Move/point UX design artifacts to design site canonical pages.
• Keep operational runbooks/version truth in docs site canonical pages.
• Add release hygiene checklist across version.json, roadmap date, and changelog deployment note.

Top 3 Priorities (Ordered)

1. P0: Auth reliability — GitHub, Telegram, admin password
2. P0: /api/status reliability and truthful degradation reporting
3. P1: Documentation IA/version-control cleanup between docs and design

Agent Directives (Parallel Thread Model)

Thread	Objective	Directive
Agent A — Auth	Restore auth reliability	Validate and fix GitHub OAuth, Telegram callback/session, and admin-password flow; produce auth matrix and root-cause notes.
Agent B — Status	Restore /api/status confidence	Audit health checks/timeouts, implement degraded vs hard-fail semantics, add regression tests.
Agent C — Docs+Design IA	Correct ownership/version control	Implement docs/design content taxonomy, versioning conventions, and discovery UX coverage in design artifacts.

Definition of Done for This Documentation Track

• Single inventory page exists with blockers + next steps.
• Docs and design pages explicitly identify ownership and versioning responsibilities.
• Discovery experience coverage includes variants, channels, intents, and ASCII frames in design artifacts.