Bootstrap HandoffStack for external Phase 3 dogfooding

[brianmsm]

Purpose

Prepare brianmsm/r-workflow-plugins to participate as the second external project in HandoffStack Phase 3 dogfooding.

This bootstrap is a prerequisite only. It is not itself a measured Phase 3 dogfood cycle and must not be counted toward the four Phase 3 incident metrics.

Exact baseline

Bootstrap only from:

main@7e2e05391942f9dfe4effbdd9b4599e6a006fc8c

Root tree:

750a63d9a23fe2d57a4a2931f831fa1c1a2f8a26

HandoffStack source to install from:

brianmsm/HandoffStack@7596e6cf8ae03f38a7606b6e4d9b29050dfc0663

Do not silently use another revision.

Repository facts to preserve

This repository already has project-owned AGENTS.md. Its current rules include keeping repository files in English, avoiding placeholder structure and overdesign, keeping plugin/skill guidance concise, and consulting the root architecture/naming/release docs before structural or release changes.

Do not replace that file with generated HandoffStack content. Merge only the concise HandoffStack integration guidance needed for future agents, preserving all existing project rules.

Current product state includes the released quarto-publishing v0.2.1; bootstrap must not change plugin versions, marketplace release refs, plugin content, skills, changelog, roadmap conclusions, or release state.

HandoffStack configuration

Install project config schema 2 with:

[profile]
base = "software"
extensions = []

Use:

• base branch main;
• normal HandoffStack branch prefix hs/;
• default logical role bindings;
• the six normal lifecycle label names;
• [semantics] requirements = [] with no project-local semantic definitions;
• [governance] files = ["AGENTS.md"].

Do not synthesize a repository-wide validation command. There is no single current repo-wide project gate established by the versioned project contract. Future tasks may specify task-specific validation, and HandoffStack semantic requirements do not invent commands.

Required bootstrap actions

1. Read the existing AGENTS.md, root README.md, docs/architecture.md, docs/naming-conventions.md, and docs/release-process.md before editing.

2. Materialize HandoffStack from the exact pinned source above and run init conservatively against this repository using profile software and base branch main.

3. Preserve all non-conflicting project files and existing project-owned guidance.

4. Merge concise HandoffStack guidance into the existing AGENTS.md rather than replacing it.

5. Install the normal HandoffStack client surfaces when safe, including .handoffstack.toml, docs/handoffstack.md, task Issue template, PR template, and recovery ignore behavior.

6. Ensure the repository defines all six lifecycle labels:

   • hs:ready
   • hs:in-progress
   • hs:review-ready
   • hs:changes-requested
   • hs:blocked
   • hs:human-review

   Label-definition creation is bootstrap infrastructure and does not put this bootstrap Issue into the lifecycle. Use normal GitHub CLI/API capability available in the local executor environment; do not create auxiliary probe branches.

7. Run HandoffStack validate from exactly 7596e6cf8ae03f38a7606b6e4d9b29050dfc0663 against the final checkout and prove the successful validate invocation is read-only using before/after Git state.

8. Perform documentation/config sanity checks appropriate to the bootstrap delta, including valid TOML/JSON where applicable and internal-path consistency. Do not fabricate a product release or run unrelated publication workflows.

Branch / PR

Use exactly one bootstrap branch:

bootstrap/handoffstack

Open exactly one draft PR against main.

This bootstrap Issue and its PR must carry no hs:* lifecycle labels. The six labels are repository definitions for future canonical tasks only.

The PR should record:

• exact base SHA/tree;
• exact final HEAD/tree;
• changed paths;
• HandoffStack pinned source;
• profile/configuration installed;
• how existing AGENTS.md was preserved/merged;
• lifecycle-label definitions verified;
• HandoffStack validate result and read-only proof;
• any additional bootstrap checks actually run.

Out of scope

Do not:

• change quarto-publishing behavior or content;
• change plugin/marketplace versions or release refs;
• create a product feature Issue inside this bootstrap;
• modify the plugin roadmap conclusions;
• add a repository-wide validation command merely for HandoffStack;
• add workflows, watchers, daemons, telemetry, MCP, or automation;
• treat this bootstrap as a measured Phase 3 cycle;
• create auxiliary branches/PRs/issues for probing or evidence.

Completion / gate

The executor stops after opening the one draft bootstrap PR and leaving complete durable evidence. Do not merge or close this Issue without explicit project-owner authorization.

After this bootstrap is reviewed and merged, a separate real product task from the existing quarto-publishing roadmap/testing work will become the first measured HandoffStack cycle in this second external project.