Molloy-Home/minions-template
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: refine downstream onboarding workflow

Browse Source
This commit is contained in:
deamonkai
2026-04-12 13:56:28 -05:00
parent e650ec65d1
commit 7dd35f3975
11 changed files with 93 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/downstream-upgrade-playbook.md
View File

@@ -25,6 +25,12 @@ first upgrade should establish one that matches the repo's current base-template
version before attempting a larger template jump. If the repo is truly new,
run the onboarding playbook first.
Both snapshot paths should contain export-ready copies of the template, not full
Git clones.
- exclude `.git/`
- exclude files marked `do-not-export` in `docs/export-manifest.md`
## Ownership
- `PM` owns the upgrade packet, merge order, and Operator-facing decision
@@ -41,9 +47,10 @@ run the onboarding playbook first.
1. Confirm the downstream repo's current base-template version in
`minion-version.md`.
2. Stage the current approved template snapshot in `.minions-template/` if it is
not already present.
3. Import the incoming template version into `.minions-template.next/`.
2. Stage the current approved export-ready template snapshot in
`.minions-template/` if it is not already present.
3. Import the incoming template version into `.minions-template.next/` using the
same export-ready filtering rules.
4. Diff `.minions-template/` against `.minions-template.next/` to see what the
template changed.
5. Use `docs/export-manifest.md` to classify each affected live file as: