53d06063-fc18-4a0f-8a00-bd7b87a7d8a5
Done
Deploy Workshop dashboard as decoupled internal service
Why GitLab Pages works as a self-service fallback. The preferred long-term path is a separate dashboard service in the same general environment as gala-brain.
Details
- Owner
- Workshop Team
- Doing
- claude-code
- Next
- No action.
- Done when
- Dashboard service runs with WORKSHOP_API_BASE_URL and a secret WORKSHOP_API_TOKEN, and can be updated independently from gala-brain deploys.
- Skills
- dashboard-publishdeployment-coordination
- Age
- 9h
- Last
- done
a6c4fe3f-880c-4315-935f-37748b1f0a1e
Done
Add URL-first agent orchestration endpoints
Why Built from Mark's goal-based flow for humans and agents using Workshop without making Mark the router.
Details
- Owner
- Workshop Team
- Doing
- Codex
- Next
- Keep browser-click testing as required proof for dashboard/UI interaction changes.
- Done when
- Commit fda5543 is pushed, CI pipeline 2641381552 passes, tests cover /agent/start, packet, claim, receipt, move, and follow-up creation, and the local dashboard service exposes th...
- Plan
- 1/1
- Skills
- agent-orchestrationdashboard-publishsafe-code-change
- Age
- 6h
- Last
- done
ce0f45e3-829e-4743-b2bf-16fc99fa7d50
Done
Simplify dashboard readability
Why Mark flagged that the dashboard looked like a confused mess and was hard to interpret at a glance. Implemented in commit af8bf3b.
Details
- Owner
- Workshop Team
- Doing
- Codex
- Next
- Use the simplified dashboard layout and keep iterating from user feedback.
- Done when
- Dashboard uses action-oriented sections, hides empty raw stages, keeps next action prominent, moves secondary metadata behind Details, and tests pass.
- Plan
- 5/5
- Skills
- dashboard-usabilitysafe-code-change
- Age
- 8h
- Last
- done
82970278-1063-408f-aaf7-9eaa7ba63f8f
Done
Add dashboard feedback form
Why Implemented in commit c59650a. The CLI feedback path exists; this adds the browser path for the long-running dashboard service.
Details
- Owner
- Workshop Team
- Doing
- Codex
- Next
- Deploy the dashboard service when we want browser feedback submission; GitLab Pages stays read-only.
- Done when
- Dashboard service renders a feedback form, POSTs feedback server-side with the existing API token, creates a feedback task, refreshes the dashboard, and tests cover the flow.
- Plan
- 5/5
- Skills
- feedback-triagedashboard-publishsafe-code-change
- Age
- 8h
- Last
- done
9a537acb-505a-4601-b05f-e234914c6593
Done
Feedback: Need task details on dashboard
Why Reporter: Joaquin Source: Slack first feedback I was able to open it, but only saw one smoke task. It would be nice to know the details of a task, like why we are doing this or wh...
Details
- Owner
- Workshop Team
- Doing
- unassigned
- Next
- Use workshop feedback for future system feedback instead of routing through Mark.
- Done when
- Feedback is triaged into an actionable task, declined with a reason, or folded into existing work.
- Plan
- 0/3
- Skills
- feedback-triageworkshop-task-authoring
- Age
- 8h
- Last
- done
aaa56950-ae54-403f-9fec-afd90110d824
Done
Improve dashboard task details after first feedback
Why Joaquin opened the first shared dashboard and asked for task details like why we are doing this and what we are trying to solve.
Details
- Owner
- Workshop Team
- Doing
- Codex
- Next
- Collect next feedback from reviewers.
- Done when
- Dashboard cards show short Why and Done when fields for tasks, and the shared dashboard is republished.
- Skills
- dashboard-publishsafe-code-change
- Age
- 9h
- Last
- done