Spaces:
Running
Running
Commit History
11 days ago
-
feat(tracker): a "cancelled" task status, closed like "done" without claiming the work was done
- schema.sql: the status check constraint is replaced (drop if exists, add) so the file stays re-runnable; the open-tasks partial index and the task_board stale flag exclude both closed statuses. - store.py: CLOSED = ("done", "cancelled"); update_task sets closed_at for either and clears it on reopen; list_tasks and open_task_by_source hide both unless include_done or the status is asked for by name. - Liveboard TML: every query that excluded done now excludes cancelled too; the model's Status description lists it. - Tool docstrings and the agent write-up (a CANCEL step beside CLOSE). - Tests: cancelled closes, hides, never goes stale, reopens; a cancelled automatic task no longer blocks a new one; the schema says what the code says. The fake client gains supabase-py's `not_` negation. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>c1d7132
23 days ago
-
feat(pipeline): the pickup run, the agent worker, and the process they implement
Every change on a branch off develop, a PR in, approved on arrival for Mike and Jack and by one of them for everyone else, picked up four times a day and pushed to the test Space. Everything that writes to GitHub or Hugging Face runs on boone's Mac under his own credentials; the server only reads. - scripts/pipeline_run.py: queue -> merges in its own pipeline/ worktree (detached, --no-ff, a conflict skips with a note) -> unit suite with the known-failures allowlist -> push origin -> three-minute idle gate on the Space -> push hf-mcp-test -> ping confirms the sha -> deployments row and "on test-mcp" notes. Never prod, never a red suite, never a non-fast- forward. --dry-run reports against the real tracker. - scripts/launchd/com.demoprep.pipeline.plist: 7:30 / 11:30 / 15:30 / 19:30 local time. scripts/pipeline_known_failures.txt: the pre-existing failures. - scripts/agent_worker.sh + agent_worker_prompt.md + tracker_cli.py: the agent's turn — top task, agent/t<id>-<slug> o…62f3e9a
25 days ago
-
feat(tracker): team tasks beside their pull requests — Supabase store, six MCP tools, GitHub sync, ThoughtSpot TML
The team (Mike, Jack, Manny, Gora) had pull requests in GitHub and nothing else: sprint notes in markdown, "ping Jack" by hand in Slack. This adds a task list in Supabase that the AgentSpot "Task Manager" agent, the Slack bot and any Claude Code session reach through the same MCP tools, with the PRs synced in beside the tasks and a ThoughtSpot Liveboard over the same rows. - demoprep_app/tracker/schema.sql: tasks, task_notes, pull_requests, tracker_people (seeded), the task_board view (PR state, days open, last note, stale), an updated_at trigger, the tracker_reader role for ThoughtSpot. Run once in the Supabase SQL editor; not run yet. - demoprep_app/tracker/store.py: list / get / create / update / add_note. An unknown person is refused, never guessed. A partly wrong request is wholly refused with every problem named and nothing written. Every reassignment, status, priority and PR link writes a note saying who. - demoprep_app/tracker/github_sync.py: daemon poller over TRA…50cb4f4