soryu/makima, branch contract-drag-reorder

feat(contracts): drag-to-reorder active contract rows in sidebar

2026-05-08T11:16:46+00:00

HTML5 drag/drop on active contract rows. Dragging a row over another in the same directive folder shows a green top-border drop indicator; dropping calls reorderDirectiveContract(id, targetPosition) and refreshes the folder. Shipped/archived rows aren't draggable (historical, ordering is fixed). Implementation: - DocumentRow gains optional draggable + drag event props. - DirectiveFolder owns the drag/over state and handleReorder callback; computes target position from the drop-target row's current position. - Repository's reorder endpoint already exists from the backbone PR and handles sibling shift in a transaction. Co-Authored-By: Claude Opus 4.7 (1M context)

feat(contracts): lifecycle — Lock/Start/Pause/Complete/Unlock + queue scheduler (#129)

2026-05-08T11:12:51+00:00

Adds the contract lifecycle layer on top of the unified-contracts backbone (#128). State machine: draft → queued → active → shipped → archived At most one contract per directive sits in `active` at any time — the queue is serialised because each directive owns a single shared worktree. Repository helpers handle the transition checks AND auto-promote the next-up `queued` contract whenever the active slot frees (pause / complete / unlock-from-active / archive-from-active). Endpoints (all under /api/v1/contracts/{id}): POST /start draft → queued | active (depending on slot) POST /pause active → queued; promotes next queued POST /complete active → shipped; optional pr_url + pr_branch POST /unlock queued | active → draft; promotes if was active Frontend wiring: * `DirectiveContractStatus` now includes `queued`. * Migration adds `queued` to the CHECK constraint on directive_documents.status. * `ContractHeader` component renders breadcrumb + status pill + status-driven action buttons + a merge-mode (shared / own_pr) radio. Merge mode is editable only while draft / queued so a running flow's branch target can't change mid-stream. * RepositoryError gains a `Validation(String)` arm; the three existing exhaustive matches (files, mesh, versions) get a 400 BAD_REQUEST response for it. Drag-to-reorder UI deferred to a small follow-up — the backend endpoint already exists from the backbone PR. Co-authored-by: Claude Opus 4.7 (1M context)

feat(directives): unified contracts surface — backbone (#128)

2026-05-08T10:29:56+00:00

This is the backbone PR for the unified directive workflow. A directive holds a sequence of contracts; each contract is a spec body whose execution drives tasks in the directive's shared worktree. Lifecycle (Lock & Start, queue scheduler, drag-reorder) lands in follow-ups. What's in this PR: - Migration adds `position` (queue order) and `merge_mode` (shared|own_pr) columns to directive_documents. The actual table rename is deferred — the legacy `contracts` table from the old contracts system still exists, and the rename collision waits for Phase 5 to drop legacy contracts. - Repository: list orders by position; create assigns next-position; update accepts merge_mode; new reorder_directive_document_position shifts siblings inside a transaction. - HTTP: endpoints aliased under /api/v1/directives/{id}/contracts and /api/v1/contracts/{id}/... with a new /contracts/{id}/reorder. - Frontend: api types renamed `DirectiveContract*` (avoiding the legacy `Contract` type collision); document-directives.tsx imports via aliases so the rest of the file is untouched. Internal struct + table names stay `DirectiveDocument` / `directive_documents` until the legacy contracts cleanup. Co-authored-by: Claude Opus 4.7 (1M context)

fix(doc-mode): make task rows clickable and render live transcript (#125)

2026-05-05T15:30:46+00:00

Task rows in the directive sidebar's `tasks/` subfolder were rendered as inert `

` elements with no click handler, and EditorShell had no branch for `selection.taskId` — so clicking a task did nothing visible. - StepRow and TaskRow are now `

fix(doc-mode): flatten sidebar list + restore right-click context menu (#124)

2026-05-02T16:47:24+00:00

Two regressions reported by the user: 1. The sidebar was grouping contracts under per-status sub-folders (active/idle/archived). The user explicitly does not want that — they want a flat list with status indicated by a colored dot on the right of each row. 2. The right-click context menu on contract rows was missing — start/pause/archive/delete/create-PR/update-PR are no longer reachable through the UI. Fixes: * Drop the SidebarGroup/bucketOf/GROUP_LABEL helpers; replace the grouped render with a flat sort by status precedence (active → paused → idle → draft → inactive → archived) then alpha by title within the same status. The existing dot-color palette is unchanged; the dot just moved from the LEFT of the contract title to the RIGHT (after the orchestrator-running pulse, when present). * Wire `onContextMenu` through SidebarProps → DirectiveFolderProps → the folder header `

fix(frontend): regenerate pnpm-lock.yaml as v6 format + pin packageManager (#123)

2026-05-02T15:50:06+00:00

Build env's pnpm warned "Ignoring not compatible lockfile" against the v9 lockfile produced by my last regen — older pnpm (8.x and below, which some build images still ship) only understands v6 lockfiles, and falls back to "no lockfile" mode which then errors under --frozen-lockfile: WARN Ignoring not compatible lockfile at /app/pnpm-lock.yaml ERR_PNPM_NO_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is absent Two-pronged fix: 1. Regenerate the lockfile in v6 format using pnpm 8.15.4 via corepack (`corepack pnpm@8.15.4 install`). The lockfile now starts with `lockfileVersion: '6.0'` again — readable by both old and new pnpm. 2. Pin `packageManager: "pnpm@8.15.4"` in package.json so build envs that respect corepack/Volta install the right version automatically instead of falling back to whatever's globally installed. Verified locally with `corepack pnpm@8.15.4 install --frozen-lockfile` (the CI command). \`tsc --noEmit\` passes. Co-authored-by: Claude Opus 4.7 (1M context)

fix(frontend): regenerate corrupted pnpm-lock.yaml (#122)

2026-05-02T15:33:51+00:00

The committed lockfile was a manual frankenstein of pnpm v6 metadata (`lockfileVersion: '6.0'` + `resolution:` blocks at the top) and v9-style snapshot entries appended below. pnpm 9 read it as a single packages: map and tripped on duplicate mapping keys (\`@floating-ui/core@1.7.5\` appeared twice; same for \`@floating-ui/utils@0.2.11\`, plus dozens of \`@lexical/*\` and \`@babel/*\` entries duplicated across the v6/v9 sections). This blew up Docker / Caddy builds: ERR_PNPM_BROKEN_LOCKFILE The lockfile at "/app/pnpm-lock.yaml" is broken: duplicated mapping key (688:3) Regenerated with \`pnpm install --no-frozen-lockfile\` against the existing package.json — net -1605 / +545 lines. \`pnpm install --frozen-lockfile\` now succeeds (the CI check), \`tsc --noEmit\` passes, \`vite build\` produces a clean bundle. Co-authored-by: Claude Opus 4.7 (1M context)

feat(doc-mode): + New contract sidebar header + + New ephemeral task per folder (#121)

2026-05-02T15:11:05+00:00

The unified surface didn't expose any way to create a new contract or a new ephemeral task — the only paths were `/directives/?document=...` or right-click context menus that no longer existed in the documents-per- directive sidebar restructure. Two new affordances: * **Sidebar header gains a "+ New" button** that opens NewContractModal (title + goal + optional repository_url). On submit calls `useDirectives.create` and navigates the user into the new directive. Header label updated from "Documents" to "Contracts" so the button's intent reads naturally. * **Each open directive folder gets a "+ New ephemeral task" button** alongside the existing "+ New document" affordance. Opens NewEphemeralTaskModal (name + plan), calls the existing `createDirectiveTask` API, navigates the user into the new task's transcript at `?task=`. NewContractModal and NewEphemeralTaskModal are local to the page — mirror the styling of the older NewTaskModal that lived here pre- restructure. ⌘/Ctrl+Enter submits. Co-authored-by: Claude Opus 4.7 (1M context)

build(server): split Dockerfiles, make ML model paths optional (#120)

2026-05-02T14:26:39+00:00

Existing Dockerfile (with LLM/STT/TTS model download) is now `Dockerfile.full`. The new top-level `Dockerfile` builds a slim image without python, without huggingface_hub, without the model download step. The slim image is the new default for users who only want the orchestration surface — the directive folder UI, the mesh/task system, the API. ## Slim Dockerfile * No python / huggingface_hub / model downloads. * Same runtime tooling as `k8s/daemon/Dockerfile` (git, gh CLI, ssh, jq, curl, ca-certs, libssl3). * Embeds the daemon binary at /app/daemon-binaries/makima-linux-x86_64 for the in-server download endpoint. * PARAKEET_MODEL_DIR / SORTFORMER_MODEL_PATH / CHATTERBOX_MODEL_DIR are intentionally NOT set — Listen and Speak return "ML models not configured" if a client tries to use them. ## ML model paths now optional `ServerArgs.parakeet_model_dir`, `parakeet_eou_dir`, `sortformer_model_path`, `chatterbox_model_dir` are now `Option` (no defaults). The bin constructor inspects them: if all four are present, configures `AppState::new`; if all four are absent, uses the new `AppState::new_slim()` which leaves `model_config = None`. The lazy load path in `get_ml_models` already returned a clean error for None. Speak (TTS) was already optional via `model_config.as_ref()` — still works. Mixed configurations log a warning and degrade to slim mode. ## Ops note The old `Dockerfile.full` retains the original behaviour for anyone who needs STT/diarization/TTS in production. CI still builds the daemon image from `k8s/daemon/Dockerfile` (untouched). Co-authored-by: Claude Opus 4.7 (1M context)

feat: multi-document directives with ephemeral task lifecycle (#119)

2026-05-02T14:07:33+00:00

* feat: soryu-co/soryu - makima: Fix folder/file naming and breadcrumb hash bugs * WIP: heartbeat checkpoint * WIP: heartbeat checkpoint * WIP: heartbeat checkpoint * feat: soryu-co/soryu - makima: Frontend: render multiple documents per directive folder * WIP: heartbeat checkpoint * WIP: heartbeat checkpoint * WIP: heartbeat checkpoint * Fix DirectiveRevision import in openapi.rs after merge * Fix document-directives.tsx merge artifacts and add inactive status