`allod pm`: install surface, workflow cutover, retirement cleanup #137

New issue

Open

opened 2026-07-31 00:53:29 +01:00 by vnprc-agent · 0 comments

vnprc-agent commented

2026-07-31 00:53:29 +01:00

Contributor

Finish the allod pm migration: the tool is ported into this repo and runs against a deployment's private state repo, but it is not yet installed by the packaging that consumes allod/tools, the operator/agent workflow is undocumented, and stale artifacts of the predecessor tool remain in the deployment that migrated.

Primary goals:

Install surface — the Nix/Home Manager packaging that consumes allod/tools installs allod pm and its runtime dependencies on the intended host and dev surfaces.
Workflow cutover — the operator/agent workflow against allod pm is documented, including the state-root default and the groom selection flags (--claude/--codex).
Retirement cleanup — stale PM-tool artifacts and references are removed from the migrating deployment's document repo, superseded PM tracking issues are reconciled or closed, and the rendered board remains reachable from the new state location.

Current state

allod pm exists: the allod dispatcher carries a pm namespace that resolves and execs pm/pm, and the implementation lives under pm/ in this repo (pm/pm, pm/render, pm/integrity-check, pm/pm.schema.json). The earlier migration milestones — moving board state into a dedicated private state repo and porting the tool here — are complete; their transition record is the predecessor issue in the migrating deployment's tracker.

Scope

In scope: packaging, workflow documentation, and predecessor-artifact retirement. Out of scope: the Go rewrite (allod/tools#103) and any change to the overlay model — the board stores issue refs, priority/grouping/gate metadata, and pending decisions, never cached issue titles, state, or bodies.

Finish the `allod pm` migration: the tool is ported into this repo and runs against a deployment's private state repo, but it is not yet installed by the packaging that consumes `allod/tools`, the operator/agent workflow is undocumented, and stale artifacts of the predecessor tool remain in the deployment that migrated. Primary goals: - **Install surface** — the Nix/Home Manager packaging that consumes `allod/tools` installs `allod pm` and its runtime dependencies on the intended host and dev surfaces. - **Workflow cutover** — the operator/agent workflow against `allod pm` is documented, including the state-root default and the groom selection flags (`--claude`/`--codex`). - **Retirement cleanup** — stale PM-tool artifacts and references are removed from the migrating deployment's document repo, superseded PM tracking issues are reconciled or closed, and the rendered board remains reachable from the new state location. ### Current state `allod pm` exists: the `allod` dispatcher carries a `pm` namespace that resolves and execs `pm/pm`, and the implementation lives under `pm/` in this repo (`pm/pm`, `pm/render`, `pm/integrity-check`, `pm/pm.schema.json`). The earlier migration milestones — moving board state into a dedicated private state repo and porting the tool here — are complete; their transition record is the predecessor issue in the migrating deployment's tracker. ### Scope In scope: packaging, workflow documentation, and predecessor-artifact retirement. Out of scope: the Go rewrite (allod/tools#103) and any change to the overlay model — the board stores issue refs, priority/grouping/gate metadata, and pending decisions, never cached issue titles, state, or bodies.

vnprc-agent referenced this issue from a commit

2026-07-31 00:54:27 +01:00

Point automated-pm at allod/tools#137 after notes#66 close