Skip to content

feat: add top-level thread actions#32

Merged
galligan merged 1 commit into
mainfrom
feat/top-level-thread-actions
Jun 5, 2026
Merged

feat: add top-level thread actions#32
galligan merged 1 commit into
mainfrom
feat/top-level-thread-actions

Conversation

@galligan

@galligan galligan commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

No description provided.

galligan commented Jun 5, 2026

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@galligan galligan marked this pull request as ready for review June 5, 2026 20:38

galligan commented Jun 5, 2026

Copy link
Copy Markdown
Contributor Author

Merge activity

  • Jun 5, 8:39 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jun 5, 8:39 PM UTC: @galligan merged this pull request with Graphite.

@galligan galligan merged commit d5e031d into main Jun 5, 2026
5 checks passed
galligan added a commit that referenced this pull request Jun 5, 2026
## Context

Implements the stable refs and flat CLI/MCP reshape from `.agents/plans/stable-refs-flat-cli/PLAN.md`, stacked on PR #32 (`feat/top-level-thread-actions`). Full Codex thread ids remain accepted; dispatch refs are stored local selectors for managed lanes; titles and `@handles` are mutable convenience labels.

## What changed

- Added dispatch-local Codex ref allocation and v3 registry migration/backfill.
- Added a shared selector resolver for refs, full ids, handles, exact titles, and read-only fuzzy title matching.
- Flattened canonical CLI routes: `attach`, `list`, `get`, `tail`, `watch`, `sync`; split persisted `tail` from bounded live `watch`.
- Renamed grouped MCP tools to `dispatch_thread_read`, `dispatch_thread_write`, and `dispatch_thread_destroy` while preserving safety annotations.
- Managed-thread outputs now consistently include identity context: `lane`, `ref`, full `id`, `title`, `handle`, `managed`, `source`, `status`, and `cwd` for send/goal/sync/tail/watch-style outputs.
- Updated schemas, tests, README, usage/design docs, ADR-0019, agent rules, skills, plugin docs, and the plan RETRO ledger.

## How to test

- `uv run pytest tests/core/test_handlers.py tests/core/test_triggers.py tests/surfaces/test_mcp_routing.py tests/surfaces/test_parity.py tests/core/test_examples.py -q`
- `uv run dispatch schema send`
- `uv run dispatch schema 'goal status'`
- `uv run dispatch schema sync`
- `uv run dispatch schema tail`
- `uv run dispatch schema watch`
- `uv run ruff check src/outfitter/dispatch tests`
- `uv run ruff format --check src/outfitter/dispatch tests`
- `uv run mypy src tests --strict`
- `just check`

## Risks / notes

- Registry schema bumps to v3 and backfills refs for existing lanes in `created_at, id` order.
- `lane` remains in these output payloads as a compatibility field for the full Codex thread id; `ref` and `id` are the stable thread-oriented fields for new consumers.
- `search --lane` and `stop --lane` remain accepted compatibility aliases, but docs teach `--thread` / positional selectors as canonical.
- CI is intentionally left in draft until checks finish green.
@galligan galligan deleted the feat/top-level-thread-actions branch June 5, 2026 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant