State the Bootstrap's Archive Live Channel in Two Skills

.agents/skills/check-this-repo/SKILL.md

@@ -33,10 +33,22 @@ repo.
    `python3 scripts/skills_install.py --report` from it. A snapshot not current, or no stamp, is very often
    the direct answer to "why isn't a fleet rule applying": the harness never loaded the current
    content in the first place, and no amount of re-reading `GOVERNANCE.md` fixes that. For a
-   Claude Code session, read `live` as well, since that channel loads the registered checkout in
-   place rather than the copy: a checkout that is missing, detached, or on an old branch is an
-   answer there whatever the exit code says, and moving that checkout is the fix rather than
-   re-installing.
+   Claude Code session, read `live` as well, since that channel loads the registered directory in
+   place rather than the copy. A registered directory that is missing is an answer there whatever
+   the exit code says.
+   - Where `live` carries `vcs: archive`, the channel serves the tree the hub's
+     `host-setup/bootstrap.sh` or `bootstrap.ps1` keeps, which has no git, so `branch: null` there
+     is not a detached checkout. A `live.commit` behind the hub's `main` is the answer, and so is
+     a null one, which means the bootstrap could not resolve the commit it fetched. Re-running
+     `bootstrap.sh --skills` or `bootstrap.ps1 -Skills` is the fix, given `--dir` or `-Dir` naming
+     the parent of `live.checkout` where an earlier run kept the tree somewhere other than the
+     default, since re-running the installer from any other directory leaves an existing
+     registration where it is.
+   - Where `live` carries no `vcs` and a non-null `commit`, it names a git checkout, and one that
+     is detached, `branch: null`, or on an old branch is an answer too, and moving that checkout
+     is the fix rather than re-installing.
+   - Any other shape names no registration, or one this report could not read, and the `reason`
+     it carries, where it carries one, says which.
 2. **Does this repo's own carried content still match the hub.** Compare `AGENTS.md`'s
    "Where the Rules Live" pointer text, and any other verbatim `AGENTS.md`/`GOVERNANCE.md` section
    this repo carries, against the same hub checkout's current wording, by reading the text rather

.agents/skills/merge-and-release/SKILL.md

@@ -129,9 +129,13 @@ skill covers all of it, scoped down by what the maintainer actually asks for.
    or ignored under `.agents/skills/` or `.claude-plugin/`, the two paths the installer reads, so
    the copy holds exactly the promoted commit. `--snapshot-only` leaves the Claude Code
    registration untouched, and that channel needs no refresh here: it loads the registered
-   checkout in place, the one `--report` names under `live`, and serves whatever it holds at read
-   time, so where that is the primary checkout on `develop`, Claude Code sessions on this machine
-   load `develop`. Then remove the worktree with
+   directory in place, the one `--report` names under `live`, and serves whatever it holds at
+   read time, so where that is the primary checkout on `develop`, Claude Code sessions on this
+   machine load `develop`. Where `live.vcs` reads `archive`, that directory is the tree the hub's
+   `host-setup/bootstrap.sh` or `bootstrap.ps1` keeps rather than a checkout, and it holds what
+   that bootstrap fetched, the commit `live.commit` names where it is not null, until
+   `bootstrap.sh --skills` or `bootstrap.ps1 -Skills` runs again, which this step does not do.
+   Then remove the worktree with
    `git worktree remove <worktree>`, whatever the report said, and report a snapshot that does not
    read current. `--report` exits on the snapshot alone. This step runs whether step 5
    or 6 dispatched, skipped, or failed a release, since it is gated only on the chosen scope,

.claude-plugin/fleet-skills/.source-digests/check-this-repo

@@ -1 +1 @@
-e44aa4df6a065a72
+da0a6b105966e75b

.claude-plugin/fleet-skills/.source-digests/merge-and-release

@@ -1 +1 @@
-b9f81e4bef9bcdea
+3beb0e0e24392be6

.claude-plugin/fleet-skills/skills/check-this-repo/SKILL.md

@@ -33,10 +33,22 @@ repo.
    `python3 scripts/skills_install.py --report` from it. A snapshot not current, or no stamp, is very often
    the direct answer to "why isn't a fleet rule applying": the harness never loaded the current
    content in the first place, and no amount of re-reading `GOVERNANCE.md` fixes that. For a
-   Claude Code session, read `live` as well, since that channel loads the registered checkout in
-   place rather than the copy: a checkout that is missing, detached, or on an old branch is an
-   answer there whatever the exit code says, and moving that checkout is the fix rather than
-   re-installing.
+   Claude Code session, read `live` as well, since that channel loads the registered directory in
+   place rather than the copy. A registered directory that is missing is an answer there whatever
+   the exit code says.
+   - Where `live` carries `vcs: archive`, the channel serves the tree the hub's
+     `host-setup/bootstrap.sh` or `bootstrap.ps1` keeps, which has no git, so `branch: null` there
+     is not a detached checkout. A `live.commit` behind the hub's `main` is the answer, and so is
+     a null one, which means the bootstrap could not resolve the commit it fetched. Re-running
+     `bootstrap.sh --skills` or `bootstrap.ps1 -Skills` is the fix, given `--dir` or `-Dir` naming
+     the parent of `live.checkout` where an earlier run kept the tree somewhere other than the
+     default, since re-running the installer from any other directory leaves an existing
+     registration where it is.
+   - Where `live` carries no `vcs` and a non-null `commit`, it names a git checkout, and one that
+     is detached, `branch: null`, or on an old branch is an answer too, and moving that checkout
+     is the fix rather than re-installing.
+   - Any other shape names no registration, or one this report could not read, and the `reason`
+     it carries, where it carries one, says which.
 2. **Does this repo's own carried content still match the hub.** Compare `AGENTS.md`'s
    "Where the Rules Live" pointer text, and any other verbatim `AGENTS.md`/`GOVERNANCE.md` section
    this repo carries, against the same hub checkout's current wording, by reading the text rather

.claude-plugin/fleet-skills/skills/merge-and-release/SKILL.md

@@ -129,9 +129,13 @@ skill covers all of it, scoped down by what the maintainer actually asks for.
    or ignored under `.agents/skills/` or `.claude-plugin/`, the two paths the installer reads, so
    the copy holds exactly the promoted commit. `--snapshot-only` leaves the Claude Code
    registration untouched, and that channel needs no refresh here: it loads the registered
-   checkout in place, the one `--report` names under `live`, and serves whatever it holds at read
-   time, so where that is the primary checkout on `develop`, Claude Code sessions on this machine
-   load `develop`. Then remove the worktree with
+   directory in place, the one `--report` names under `live`, and serves whatever it holds at
+   read time, so where that is the primary checkout on `develop`, Claude Code sessions on this
+   machine load `develop`. Where `live.vcs` reads `archive`, that directory is the tree the hub's
+   `host-setup/bootstrap.sh` or `bootstrap.ps1` keeps rather than a checkout, and it holds what
+   that bootstrap fetched, the commit `live.commit` names where it is not null, until
+   `bootstrap.sh --skills` or `bootstrap.ps1 -Skills` runs again, which this step does not do.
+   Then remove the worktree with
    `git worktree remove <worktree>`, whatever the report said, and report a snapshot that does not
    read current. `--report` exits on the snapshot alone. This step runs whether step 5
    or 6 dispatched, skipped, or failed a release, since it is gated only on the chosen scope,

.github/skills/check-this-repo/SKILL.md

@@ -33,10 +33,22 @@ repo.
    `python3 scripts/skills_install.py --report` from it. A snapshot not current, or no stamp, is very often
    the direct answer to "why isn't a fleet rule applying": the harness never loaded the current
    content in the first place, and no amount of re-reading `GOVERNANCE.md` fixes that. For a
-   Claude Code session, read `live` as well, since that channel loads the registered checkout in
-   place rather than the copy: a checkout that is missing, detached, or on an old branch is an
-   answer there whatever the exit code says, and moving that checkout is the fix rather than
-   re-installing.
+   Claude Code session, read `live` as well, since that channel loads the registered directory in
+   place rather than the copy. A registered directory that is missing is an answer there whatever
+   the exit code says.
+   - Where `live` carries `vcs: archive`, the channel serves the tree the hub's
+     `host-setup/bootstrap.sh` or `bootstrap.ps1` keeps, which has no git, so `branch: null` there
+     is not a detached checkout. A `live.commit` behind the hub's `main` is the answer, and so is
+     a null one, which means the bootstrap could not resolve the commit it fetched. Re-running
+     `bootstrap.sh --skills` or `bootstrap.ps1 -Skills` is the fix, given `--dir` or `-Dir` naming
+     the parent of `live.checkout` where an earlier run kept the tree somewhere other than the
+     default, since re-running the installer from any other directory leaves an existing
+     registration where it is.
+   - Where `live` carries no `vcs` and a non-null `commit`, it names a git checkout, and one that
+     is detached, `branch: null`, or on an old branch is an answer too, and moving that checkout
+     is the fix rather than re-installing.
+   - Any other shape names no registration, or one this report could not read, and the `reason`
+     it carries, where it carries one, says which.
 2. **Does this repo's own carried content still match the hub.** Compare `AGENTS.md`'s
    "Where the Rules Live" pointer text, and any other verbatim `AGENTS.md`/`GOVERNANCE.md` section
    this repo carries, against the same hub checkout's current wording, by reading the text rather

.github/skills/merge-and-release/SKILL.md

@@ -129,9 +129,13 @@ skill covers all of it, scoped down by what the maintainer actually asks for.
    or ignored under `.agents/skills/` or `.claude-plugin/`, the two paths the installer reads, so
    the copy holds exactly the promoted commit. `--snapshot-only` leaves the Claude Code
    registration untouched, and that channel needs no refresh here: it loads the registered
-   checkout in place, the one `--report` names under `live`, and serves whatever it holds at read
-   time, so where that is the primary checkout on `develop`, Claude Code sessions on this machine
-   load `develop`. Then remove the worktree with
+   directory in place, the one `--report` names under `live`, and serves whatever it holds at
+   read time, so where that is the primary checkout on `develop`, Claude Code sessions on this
+   machine load `develop`. Where `live.vcs` reads `archive`, that directory is the tree the hub's
+   `host-setup/bootstrap.sh` or `bootstrap.ps1` keeps rather than a checkout, and it holds what
+   that bootstrap fetched, the commit `live.commit` names where it is not null, until
+   `bootstrap.sh --skills` or `bootstrap.ps1 -Skills` runs again, which this step does not do.
+   Then remove the worktree with
    `git worktree remove <worktree>`, whatever the report said, and report a snapshot that does not
    read current. `--report` exits on the snapshot alone. This step runs whether step 5
    or 6 dispatched, skipped, or failed a release, since it is gated only on the chosen scope,