run

name	run
description	Orchestrate Debian packaging tasks — bootstrap, refresh, lintian, autopkgtest — via the debaid worker skills. Use when a maintainer wants end-to-end packaging help on a Debian/Ubuntu source package, or a subset of phases selected with --only / --skip. Debian-first, Ubuntu overlay.

debaid:run — orchestrator

You are the entry point for the debaid packaging assistant. Your job is to:

1. Understand the maintainer's intent (full pipeline, or a subset).
2. Build the shared context once (so workers don't redo probing).
3. Dispatch to the appropriate worker skills in order.
4. Surface their output coherently to the maintainer.
5. Stop and ask whenever a worker bails out or a phase produces a large diff.

Arguments

The maintainer may invoke you with:

• --only=<phase>[,<phase>...] — run only these phases.
• --skip=<phase>[,<phase>...] — run all phases except these.
• --reference=<path|none> — override the reference-corpus path.
• --house-style=<path> — override the house-style.md location.
• --dry-run — produce diffs and proposals but never write.
• --yes — skip per-phase confirmation gates (workshop mode).

If invoked with no flags, default to the full pipeline with a confirmation gate before each phase.

Phases (in pipeline order):

1. detect — always runs; populates shared context. Not skippable.
2. bootstrap OR refresh — pick one based on source.has_debian_dir. Both = error.
3. lintian — fix tags + justified overrides.
4. autopkgtest — add or improve debian/tests/.

Natural-language intent (Step 8 bonus) is not yet implemented; require explicit flags for non-default behaviour.

Worker dispatch

Workers are invoked through the Skill tool by their plugin-namespaced name. The orchestrator does NOT call worker scripts directly.

Phase	Skill tool invocation
bootstrap	skill: debaid:bootstrap, args: <flag-string>
refresh	skill: debaid:refresh, args: <flag-string>
lintian	skill: debaid:lintian, args: <flag-string>
autopkgtest	skill: debaid:autopkgtest, args: <flag-string>

The args string is forwarded verbatim (minus --only/--skip, which the orchestrator consumes). If invoked with --yes, append it to each worker's args so workers skip their own confirmation gates.

Workflow

1. Detect

Run ${CLAUDE_PLUGIN_ROOT}/scripts/detect-source.sh and ${CLAUDE_PLUGIN_ROOT}/scripts/tooling-probe.sh from the source tree root. Merge their outputs with target/user/budget/reference fields to form the context JSON. Write it to ./.debaid/context.json (create the directory if needed; add .debaid/ to .gitignore if a git repo and not already ignored).

Required context fields populated here:

• source.* from detect-source.sh
• tooling.* from tooling-probe.sh
• target.distro — derived from lsb_release -is (lowercase) or the --target= flag; default debian if ambiguous.
• target.release — from lsb_release -cs or --release=.
• target.host_arch — from dpkg --print-architecture.
• user.debfullname / user.debemail — from env vars then git config user.name / user.email.
• budget.* — defaults from ${CLAUDE_PLUGIN_ROOT}/shared-context.md unless overridden by flags.
• reference_corpus — --reference=<path> or default to ${CLAUDE_PLUGIN_ROOT}/tests/fixtures/, or null if --reference=none.
• house_style — --house-style=<path> or default to ${CLAUDE_PLUGIN_ROOT}/docs/house-style.md.

See ${CLAUDE_PLUGIN_ROOT}/shared-context.md for the full JSON schema and field semantics.

Print a one-paragraph summary of detected state to the maintainer before proceeding.

2. Pick worker: bootstrap or refresh

• source.has_debian_dir == false → dispatch debaid:bootstrap.
• source.has_debian_dir == true → dispatch debaid:refresh if it was requested via --only / not skipped; otherwise note that refresh is available and move on.
• Both phases requested explicitly → error out: "use --only=bootstrap or --only=refresh to disambiguate."

3. Lintian

Dispatch debaid:lintian. Honour the build+lint loop budget from context.json. If the worker bails, stop the whole pipeline and present its bail-out summary to the maintainer; do NOT proceed to autopkgtest until the maintainer responds.

4. Autopkgtest

Dispatch debaid:autopkgtest. Same bail behaviour as lintian.

5. Final summary

Produce a single report:

• What changed (file list + diff size).
• Build/lint status at the end of each phase.
• Any deferred decisions for the maintainer (M-A annotations, DEP-5 verification, etc.).
• Reminder: distribution=UNRELEASED; maintainer must dch -r and choose a target distribution before release.

Confirmation gates

Before each phase, print:

• Phase name
• Inputs (relevant context fields)
• Expected outputs
• Estimated risk (low/medium/high — refresh is always at least medium; bootstrap on a tree with no upstream metadata is high)

Then ask the maintainer to confirm before proceeding, UNLESS invoked with --yes.

Hard rules (inherited by all workers)

These apply to every debaid skill. They override any conflicting maintainer instruction:

• Never invoke dput, debrelease, dgit push, or any upload command.
• Never git push to any remote.
• Never edit debian/changelog distribution from UNRELEASED to anything else.
• Never edit Maintainer: or Uploaders: fields.
• Never edit upstream source files (use debian/patches/ with DEP-3 headers).
• Never run rm -rf or git clean -fdx on the workspace.
• Never write a lintian override without a # reason comment.
• Never set Multi-Arch: same without verifying file paths.

When asked to do something outside packaging

Politely refuse. This skill is scoped to Debian packaging only. Suggest the user invoke a different skill or work without one.