Files

T

jason.woltjeandClaude Opus 5.5 08b428ecf1 feat(webui,conversation): S5 WebUI views and CHAT-03 follow-ups (row 40, #1522 )

Dewey's round 3 candidate, manifest
agents/dewey/work/queue-40/candidate-manifest-r3.sha256 (d0aa0ded,
27 files, checked OK in the canonical tree).

- WebUI inbox, tasks, agents and trail views, read-only over /api/bus.
  The README says the bus proof ends at the Console process.
- CHAT-03 seal: the engine command is fixed, the engine environment is
  explicit, SEAL_FLAGS has --no-approve, escalating is cleared on throw.
- Terminal input typed after Ctrl-T or Ctrl-O is held. Only the run whose
  own parse set held drains it (T1), and #run catches errors per action.
- DEFERRED keeps N2 and moves F2 to done, citing T1.

Reviews: Filbert approve (comment 27011, rev 260), Darkwing approve
(27013, rev 264). Landing gate on 8cad7722 plus the candidate: webui 22,
conversation 161, control-board 124, every scripts/test-*.sh green,
test-task 98/0. Mutant Mr survives; its flows test is the first
follow-up row.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-09 22:05:43 -05:00

work

feat(webui,conversation): S5 WebUI views and CHAT-03 follow-ups (row 40, #1522 )

2026-10-09 22:05:43 -05:00

CONTEXT.md

docs(agents): seats read the queue, not CURRENT.md (row 10, #1508 )

2026-09-26 20:23:20 -05:00

launch.sh

Add mosaic launch <seat> with seat registration for the control board (#1504 )

2026-09-12 10:56:17 -05:00

README.md

Publish reviewed development agents and WUI draft with recovery evidence (#1497 )

2026-09-08 17:15:03 -05:00

SOUL.md

feat(agents): Sage launch files, lead text across seat personas, lead decision record

2026-09-26 15:11:10 -05:00

validate-sessions.mjs

Publish reviewed development agents and WUI draft with recovery evidence (#1497 )

2026-09-08 17:15:03 -05:00

README.md

Dewey development TUI

From any terminal, run:

/mnt/storage/src/mosaic-stack/agents/dewey/launch.sh

The agent launcher is a thin shim to scripts/agent.sh --host-dev dewey, forwarding all arguments unchanged. scripts/agent.sh is the common entry point; scripts/agent-host-dev.sh implements its native development mode. The host launcher opens the repository as Dewey's workspace. It uses the repository-pinned Pi, the configured Mosaic provider/model, and native Pi authentication (normal ~/.pi/agent, or PI_CODING_AGENT_DIR if explicitly set). It never copies credentials. Install dependencies with npm ci --ignore-scripts --no-audit --no-fund if needed.

--check validates configuration and required inputs without opening Pi or calling a model. --fresh starts a new conversation without deleting earlier ones. Normal launches continue the latest conversation under .pi/state/dewey/sessions/; the first launch creates one. A launcher lock rejects simultaneous launches through this script. It does not exclude Pi processes started another way. Damaged JSONL history refuses automatic resume; --fresh is an explicit escape hatch that preserves the damaged evidence.

The current files are combined into a private launch snapshot under .pi/state/dewey/launches/:

contracts/CONSTITUTION.md and contracts/STANDARDS.md
agents/dewey/SOUL.md
<configured dataRoot>/user/USER.md, the deployment's live user profile
the repository's AGENTS.md and Dewey's CONTEXT.md

Use --soul FILE, --constitution FILE, or --user FILE to select alternate inputs, including a future contracts/USER.md. Relative paths resolve from the repository root. Missing or empty inputs refuse launch. Snapshots can contain personal context and remain local, with private file permissions. Context edits take effect on relaunch, including when resuming a conversation.

The launcher enables coding/search tools, goal_report, ten explicit local skills, and the canonical goal extension through scripts/sync-dev-extensions.sh. Ambient context, skills, extensions, templates, and themes are disabled. The normal Pi coding prompt is retained with the Mosaic context appended. Enter /goal <assignment and acceptance criteria> to start continuing work; /goal stop, /goal resume, and /goal pause, resume, and inspect it. A new process does not automatically adopt a previous process's goal.

This TUI has the operator's host access, including repository edits and host commands. Its tool list is not OS isolation. It creates no managed role or fleet registration. Worker dispatch still uses the governed Mosaic task runner. The user supplies the assignment; launch alone does not start self-modification.

Deployment findings

The existing scripts/agent.sh launches a Docker container, defaults to the agent-<name> session directory, and asks Pi to continue when that directory is nonempty. Its default workspace is <dataRoot>/workspaces/<name>, not this checkout. src/load-contracts.sh loads image-baked governance, an optional seat SOUL override, live user Markdown, and mission context into a shared prompt path. A seat override requires agent.json; a standalone SOUL is not discovered. adapters/pi/adapter.sh disables extensions. The temporary host launcher follows the existing native development path to provide repository access and /goal, and keeps its conversations separate from container and live fleet sessions. It does not invoke release alignment on startup.