2 Commits

Include renames

Author	SHA1	Message	Date
Omar SobhandClaude Opus 5	2c7d619cf0	fix(scheduler): a firing could be lost between rescheduling and dispatch ... `tick` advanced `next_run_at` before dispatching the work, with nothing recording that the occurrence was owed. A process that died between the two dropped it silently. The window is narrower than it first looks — `claim_due` sets `last_run_at` but does not clear `next_run_at`, so a crash *before* `set_next_run` leaves the routine due and it re-fires on the next tick. The loss is specifically between the reschedule and the dispatch. That is tolerable for a message routine and not tolerable for a scheduled mission, which is why this lands before mission scheduling does. `routine_fires` holds one row per (routine, occurrence), claimed before dispatch and settled after: - Fresh — nobody has it; fire. - Retry — claimed, never settled: a crash mid-fire. Safe to fire again, as no completion was recorded and nothing downstream saw a result. - Settled — already dispatched; advance the clock and do not run the work. This is what keeps a scheduled mission to one container across restarts. A failed dispatch settles terminally rather than staying retryable. Retrying a persistently failing action every tick is how a broken routine becomes a denial-of-service against whatever it talks to; the error is kept on the row. The claim uses `xmax = 0` to distinguish a real insert from a no-op update in a single statement — `ON CONFLICT DO NOTHING` returns no row at all, so two schedulers racing one occurrence could both read it as unclaimed. Also: fan-out capped at 25 per tick with the remainder logged and deferred (a clock jump or an accidental every-minute cron would otherwise dispatch every missed occurrence at once — one container each for topology routines), and `spawn` no longer discards tick errors, so a scheduler that has stopped firing no longer looks identical to one with nothing to do. The pre-existing exactly-once test still passes: the claim changes recoverability, not firing semantics. Co-Authored-By: Claude Opus 5 <[email protected]>	2026-08-01 18:50:11 -07:00
Omar SobhandClaude Fable 5	add4f79fed	Rebrand: TeamClaw -> Clawmates (clawmates.work) ... Full-depth rename per the approved plan; the 'claw' product vocabulary (claws, /claws routes, clawId, Claw Chat) stays — it is now the brand. - Display brand: Clawmates (manifest, titles, hero, login/rail logo 'clawmates'); default host app.clawmates.work; registry ghcr.io/clawmates - Crates tc-* -> cm-* (16 crates + all imports); binaries clawmates-server/broker/bundler; images clawmates/*; env prefix CLAWMATES_* (+ CM_TEST_DATABASE_URL / CM_LIVE_LLM); config clawmates.toml; helm chart deploy/helm/clawmates with clawmates-* resources; db names clawmates*; sockets /run/clawmates; cookie cm_session; kind cluster clawmates-test; seccomp node profile clawmates-agent-profile.json - All 9 Playwright brand assertions updated in lockstep; historical spec document left untouched as the only remaining 'TeamClaw' - Local env migrated: dev pg clawmates-dev-pg/clawmates_dev, shared test server clawmates-test-pg, kind cluster recreated with image + profile, compose images rebuilt under clawmates/* Verified end to end: 161 Rust + 68 frontend tests, 29 Playwright journeys, 4 live kind tests, helm/install/LOC/placeholder gates, and the clean-room install rehearsal serving the clawmates login page from a signed bundle of the rebuilt images. Co-Authored-By: Claude Fable 5 <[email protected]>	2026-06-10 12:31:25 -05:00