Feat: RepoMan — multi-owner automation interface

[rubambiza]

Tracks implementation of the RepoMan architecture: wrapping the existing scanner/fixer programs behind a discover/onboard/configure/schedule interface, and replacing the single-$ORG + flat $REPOS_DIR identity model with per-repo {owner, name} tuples from a user-managed ~/.repoman/repos.json.

Spec: docs/specs/2026-08-27-repoman-architecture.md (in review as #67).
Motivating discussion: #62. Related issues: #65, #39.

Releases

• v0.1.0 is the first shippable RepoMan, covering the 8 implementation phases from the spec.
• v0.1.1 captures hardening surfaced during spec review. Those items are blocked by their related v0.1.0 phase and are meant to be resolved after v0.1.0 lands, so they stay open long-term.

Sub-issues

GitHub also renders these as a native sub-issue list below. Titles and state expand automatically from the references.

v0.1.0 phases

• Feat: per-repo owner/name input model (Phase 1) #78
• Feat: ~/.repoman config and setup flow (Phase 2) #73
• Feat: per-program capability check (Phase 3) #74
• Feat: repo-sync skill + owner-namespaced clone cache (Phase 4) #75
• Feat: _index.json + dashboard wiring (Phase 5) #76
• Feat: skill _meta.json + pinned-SHA attribution (Phase 6) #77
• Chore: standardize state.json schema across programs #79

v0.1.1 hardening (blocked by a v0.1.0 phase)

• Fix: sync must restore repos to main branch before syncing #80 (blocked by Phase 4, Feat: repo-sync skill + owner-namespaced clone cache (Phase 4) #75)
• Feat: fixer tracks its PR to conclusion and rebases when behind #81 (blocked by Phase 1, Feat: per-repo owner/name input model (Phase 1) #78)

Not tracked here

GitHub App auth (acting as an app instead of the clawgenti bot user) is filed as a separate research spike, #82, since it is cross-cutting infrastructure that may become its own epic.

Assisted-By: Claude Code