5 Commits

Include renames

Author	SHA1	Message	Date
Omar Sobh	8a4e222aec	research: auto-transition processing → reviewing on last run ... Hooks the topology_worker's post-terminal path into a new notify_run_completed repo helper that atomically transitions the topic processing → reviewing when the completed run has research_topic_id set AND no siblings for that topic are still queued or running. Guarded on status='processing' so a retry, a re-fire, or a topic already past processing are all no-ops. Best-effort at the worker; DB hiccups are logged and never fail the run. The manual /submit-review endpoint stays as an escape hatch for topics that end up parked in processing with nothing to complete (updated the doc comment).	2026-07-06 12:32:18 -07:00
Omar Sobh	6d1dda6197	loops: iteration timeline — GET /api/topology-runs?loop_id=X ... Extend the topology-runs list route with an optional loop_id filter that returns iterations for a single loop, newest-iteration-first. Adds the iteration and finished_at columns to the summary (skip-null on the JSON so compares stay compact). Backed by list_by_loop in the repo, which uses the existing topology_runs_loop_idx partial index. LoopsCanvas fetches the runs in parallel with the loop detail and renders an iteration timeline card (iteration #, status pill, start time, duration, run id prefix) between the graph section and the actions row.	2026-07-06 12:28:34 -07:00
Omar SobhandClaude Opus 4.8	3eca4ed70c	Recursive deploy ladder: Company + Org tiers, mesh mark, two-tier rail ... Completes the scale ladder (single → team → company → org). Every tier is a topology whose nodes are the tier below; running a parent recursively runs each child's sub-topology down to the leaf claws. Backend: - migration 0011: companies/company_teams, orgs/org_companies, topology_runs.tier - cm-db repos for companies + orgs (mirror teams) - TurnRequest.attrs (forwarded from node.attrs) for child-id binding - SubTopologyExecutor (recursive_exec.rs): a parent "turn" runs the child's sub-topology; durability via parent updated_at keepalive + cancel propagation + depth cap; boxed future breaks the org→company recursion - topology_worker selects executor by job.tier - routes: /api/companies, /api/orgs (create/list/get/run) + unified /api/structure/{level}/{id} for the zoom canvas Frontend: - MeshMark: node-mesh brand glyph (replaces the claw PNG), tier variants - TopologyGraphView: optional onNodeClick/nodeMeta + dark-token theming - StructureCanvas + Breadcrumb: one recursive zoom view for every tier (drill down on node click, breadcrumb up); TeamRunPanel extracted + shared - two-tier Discord-style rail: StructureRail (mesh mark + org/company/team glyphs + tools popover + deploy + user) | RosterColumn (selected group's children, or your claws); SecondaryNav for cross-cutting tools - ComposeWizard (company/org) wired into DeployWizard; /companies + /orgs pages Co-Authored-By: Claude Opus 4.8 <[email protected]>	2026-06-18 14:25:06 -07:00
Omar SobhandClaude Opus 4.8	6e87433c66	Close gaps: GLM-judge (anthropic registry) + run cancel + deep-link ... #2 GLM judge (closes #114): registry NamedProvider gains a `format` field; build_provider_registry builds an AnthropicProvider for format="anthropic". GLM's coding/OpenAI endpoint is ToS-throttled for raw SDK, but its Anthropic endpoint (api.z.ai/api/anthropic) accepts raw API calls (verified x-api-key -> glm-4.7), so CLAWMATES_JUDGE_MODEL=glm:glm-4.7 routes the door governor / topology judge through GLM with no runtime-routing. (Kimi-as-judge still needs a Platform key — coding key is agent-only.) #3 run-control: POST /api/topology-runs/{id}/cancel (workspace-scoped, queued/running only); the worker honors it at the step boundary (checks current_status in the checkpoint callback) and won't clobber a cancel with `failed`. Frontend Run tab gains a Cancel button and clickable recent runs that deep-link into a live/replayed stream (SSE replays from checkpoint). cm-* tests (incl. new cancel test) + clippy + frontend lint/typecheck green. Co-Authored-By: Claude Opus 4.8 <[email protected]>	2026-06-18 03:07:41 -07:00
Omar SobhandClaude Opus 4.8	272669e1f5	Durable topology jobs (3+4/4): background worker + async run API ... POST /api/topologies/run now ENQUEUES a durable job and returns 202 {run_id, status:queued} instead of executing inside the HTTP request — the prerequisite for long-horizon runs (no client/proxy/LB timeout, survives restarts). topology_worker: a spawned loop that requeues stale running jobs, claims the next queued one (CAS via FOR UPDATE SKIP LOCKED), drives it through execute_resumable, and checkpoints RunProgress after every step; on crash the stale sweep requeues it and the next claim resumes from the last checkpoint. Wired into server startup beside the scheduler + resume sweeper. GET /api/topology-runs/{id} now reports lifecycle status/kind/error/checkpoint + the result blob (kept the `comparison` field name for back-compat with the compare UI; null until completed). list_runs includes status + kind. Tests: durable lifecycle (enqueue→claim→checkpoint→complete) + stale-requeue resume, both green; p0 endpoints (compare path) unchanged. 13 + 2 tests pass, clippy clean. Co-Authored-By: Claude Opus 4.8 <[email protected]>	2026-06-17 19:12:54 -07:00