4 Commits

Include renames

Author	SHA1	Message	Date
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	8dee01c77b	Durable topology jobs (1/4): job-table schema + repo ... Evolve topology_runs into a durable-job table (migration 0009): status state machine (queued/running/completed/failed/cancelled), kind, input graph, per-step checkpoint, error, last_event_id, timestamps. comparison becomes nullable (the result blob, absent until completion). Back-compat: existing rows default to completed/compare. cm-db repo gains the durable-job ops: enqueue_run, claim_next_queued (CAS via FOR UPDATE SKIP LOCKED), checkpoint, complete, fail, requeue_stale (resume sweep), and status(). Regenerated .sqlx cache. Also fix two pre-existing test RuntimeConfig literals missing the providers field (from the registry work). Co-Authored-By: Claude Opus 4.8 <[email protected]>	2026-06-17 19:02:32 -07:00
Omar SobhandClaude Opus 4.8	7baf2082d0	feat(topology): persist comparison runs + history ... Save each comparison and let users reload past ones. - migration 0008: topology_runs (workspace-scoped; full comparison as JSONB). - cm-db repo::topology_runs (insert / list_recent / get) + regenerated .sqlx. - cm-api: compare persists best-effort (never loses the LLM result on a DB hiccup); GET /api/topology-runs (recent) + GET /api/topology-runs/{id}. Integration test asserts persist → list → get. - frontend: "Recent comparisons" list on the Compare tab; click to reload a saved run. e2e p8 green (39 suite); offline build + clippy clean. Server self-migrates at boot (cm_db::MIGRATOR), so 0008 applies on deploy. Co-Authored-By: Claude Opus 4.8 <[email protected]>	2026-06-16 05:11:52 -07:00