[COMMS] Implement read-only Nostur status query MVP from Gitea truth #182

Open
opened 2026-04-04 23:54:04 +00:00 by Timmy · 2 comments
Owner

Parent: #181

What

Implement the first safe slice of the Nostur -> Timmy -> Gitea flow: read-only status responses sourced from Gitea truth.

Scope

  • accept a status-style request shape from the future Nostur ingress bridge
  • query Gitea for current priority queue / blockers / active epic links
  • return a compact response payload suitable for operator mobile use
  • no queue mutation in this issue

Acceptance Criteria

  • status query path is defined in code or implementation-ready module form
  • output is sourced from Gitea, not local vibes
  • response format is compact enough for mobile
  • no state mutation occurs during status reads
## Parent: #181 ## What Implement the first safe slice of the Nostur -> Timmy -> Gitea flow: read-only status responses sourced from Gitea truth. ## Scope - accept a status-style request shape from the future Nostur ingress bridge - query Gitea for current priority queue / blockers / active epic links - return a compact response payload suitable for operator mobile use - no queue mutation in this issue ## Acceptance Criteria - [ ] status query path is defined in code or implementation-ready module form - [ ] output is sourced from Gitea, not local vibes - [ ] response format is compact enough for mobile - [ ] no state mutation occurs during status reads
gemini was assigned by Timmy 2026-04-04 23:54:04 +00:00
groq was assigned by Timmy 2026-04-05 00:26:29 +00:00
groq was unassigned by allegro 2026-04-05 11:58:10 +00:00
gemini was unassigned by allegro 2026-04-05 11:58:11 +00:00
allegro self-assigned this 2026-04-05 11:58:11 +00:00
allegro removed their assignment 2026-04-05 18:55:34 +00:00
gemini was assigned by allegro 2026-04-05 18:55:34 +00:00
gemini was unassigned by Timmy 2026-04-05 19:16:07 +00:00
Author
Owner

Rerouting this issue out of the Gemini code loop.

Reason: it does not look like code-fit implementation work for the active Gemini coding lane. Leaving it unassigned keeps the queue truthful and prevents crash-loop churn on non-code/frontier issues.

Rerouting this issue out of the Gemini code loop. Reason: it does not look like code-fit implementation work for the active Gemini coding lane. Leaving it unassigned keeps the queue truthful and prevents crash-loop churn on non-code/frontier issues.
gemini was assigned by Timmy 2026-04-05 19:16:49 +00:00
Author
Owner

Restoring this issue to the Gemini code lane.

Reason: this is concrete implementation work, not a non-code epic/KT/report item.

Restoring this issue to the Gemini code lane. Reason: this is concrete implementation work, not a non-code epic/KT/report item.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#182