Define a RepoKit labelling standard (issues/PRs) with per-repo bootstrap

[PBNZ]

Retrospective finding — refs #10.

Context

RepoKit standardises commits, changelogs, docs and checklists — but says nothing about issue
labels. In practice, repos either run GitHub's stock labels untouched or invent a local scheme
mid-project; cross-repo project boards then have no consistent vocabulary to filter on. A
standard needs to work for both public and private repos, for solo repos and for multi-person
board-driven ones, without adding ceremony to repos that barely use issues.

Proposal

A standard/labels.md reference defining a small layered scheme:

• Keep GitHub defaults (bug, enhancement, documentation, question, …) as the base —
  they cost nothing and external contributors know them.
• Namespace conventions (adopt only the namespaces the repo needs):
  • area:<topic> — repo-defined functional areas; the namespace is standard, values are local.
  • agent:<name> — work authored/held by an AI agent (e.g. agent:claude).
  • Workflow verdicts for board-driven repos: rework (implementation failed review),
    needs-respec (spec was wrong — back to backlog), blocked.
  • campaign:<name> (or similar) — time-boxed cross-cutting efforts (an audit's follow-up
    batch), so they can be swept in one filter.
• Fixed colours per namespace so labels read the same across repos.
• Bootstrap: a documented one-liner (gh label clone or a small script in scripts/) to
  apply the set to a new or existing repo; scaffolding applies it automatically.

Tasks

• Author standard/labels.md (scheme, colours, when to adopt which namespace).
• Add label bootstrap to the scaffold flow + a retrofit one-liner for existing repos.
• Cross-reference from the board/workflow guidance so rework/needs-respec semantics are
  defined in exactly one place.

Acceptance criteria

• A new scaffolded repo gets the base set automatically; an existing repo can adopt it with one
  command.
• The scheme is documented as layered/opt-in — a solo private repo is compliant with defaults
  only.

— 🤖 Claude, on behalf of @PBNZ

[PBNZ]

Triage: accepted (adapted: bootstrap hooks into the existing opt-in remote-creation step, since labels need a remote to exist).

Landed on PR #18 (commit 58fcd66): standard/labels.md — GitHub defaults as the compliant base, opt-in area:/agent:/campaign: namespaces with fixed colours, workflow-verdict labels (rework/needs-respec/blocked) defined there once, and an idempotent gh label create --force bootstrap block (+ gh label clone for repo-to-repo). agent-collaboration.md cross-references the verdict semantics rather than redefining them.

— 🤖 Claude, on behalf of @PBNZ

[PBNZ]

Verified on main (f7ab31c): standard/labels.md present, routed from the skill, bootstrap wired into the /new-repo remote step. Closing on @PBNZ's instruction.

— 🤖 Claude, on behalf of @PBNZ