Add Immich MCP tickets and execution order #91

Merged

ryan merged 2 commits from docs/immich-mcp-tickets into main 2026-10-13 09:23:20 -04:00

Conversation 0 Commits 2 Files Changed 1

+789

ryan commented 2026-10-13 09:08:23 -04:00

Owner

Copy Link

Copy Source

Adds docs/immich-mcp/tickets.md, which breaks the merged design (#90) into eight tickets.

Order:

1. IMM-01: verify production Immich and create scoped keys (conductor).
2. IMM-02 ∥ IMM-03: server foundation, trip summaries.
3. IMM-04 ∥ IMM-05: read tools, raggr wiring.
4. IMM-06: write tools.
5. IMM-07: docs.
6. IMM-08: live verification (conductor).

Each ticket lists its branch, base, dependencies, exact files with line anchors, what must not change, implementation details, tests that must fail without the change, and acceptance criteria.

It also writes down the Herdr rules we use:

• The conductor pane plans and hands each ticket to a Sonnet worker in its own worktree.
• Workers never commit or push.
• The conductor reviews every ticket twice (round two verifies round one; any remaining bug the conductor fixes itself), then ships one PR per ticket via tea, in merge order, and cleans up.

🤖 Generated with Claude Code

Adds `docs/immich-mcp/tickets.md`, which breaks the merged design (#90) into eight tickets. **Order:** 1. IMM-01: verify production Immich and create scoped keys (conductor). 2. IMM-02 ∥ IMM-03: server foundation, trip summaries. 3. IMM-04 ∥ IMM-05: read tools, raggr wiring. 4. IMM-06: write tools. 5. IMM-07: docs. 6. IMM-08: live verification (conductor). Each ticket lists its branch, base, dependencies, exact files with line anchors, what must not change, implementation details, tests that must fail without the change, and acceptance criteria. It also writes down the Herdr rules we use: - The conductor pane plans and hands each ticket to a Sonnet worker in its own worktree. - Workers never commit or push. - The conductor reviews every ticket twice (round two verifies round one; any remaining bug the conductor fixes itself), then ships one PR per ticket via `tea`, in merge order, and cleans up. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ryan added 1 commit 2026-10-13 09:08:24 -04:00

Add Immich MCP tickets and execution order ... 29200e49db

Breaks the merged design into eight tickets (IMM-01..08) with files,
steps, tests and acceptance criteria, the wave order with what can run
in parallel, and the Herdr conductor/worker rules used to build them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

ryan added 1 commit 2026-10-13 09:20:37 -04:00

Record Immich 3.3.1 and make the conductor sole owner of tickets.md ... 609ee5aa7e

Production Immich is reachable at immich.ryanjchen.com and runs 3.3.1,
so the filter API style is the default and the public URL is known.
Parallel ticket PRs editing one status file would conflict, so only the
conductor updates tickets.md, once per wave.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

ryan merged commit 466892de97 into main 2026-10-13 09:23:20 -04:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

ryan

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: ryan/simbarag#91