Fix Mid-Sentence Line Wraps Copilot Caught on the Promotion PR

.agents/skills/resync-a-repo/SKILL.md

@@ -49,21 +49,7 @@ Preserve the evidence RESYNC.md section 2 requires, and do not leave the finding
 
 ## Apply, in this order
 
-1. **The instruction set first.** `CLAUDE.md`, then `AGENTS.md` and `GOVERNANCE.md` verbatim
-   sections, then `CODESTYLE.md` and `WORKFLOW.md`, including the `AGENTS.md` skill-dependency
-   pointer paragraph (naming `scripts/skills_install.py` and where the fleet's Skills live) as
-   one more verbatim unit carried in this same step, not a separate pass. `CLAUDE.md` is the
-   single `@AGENTS.md`-import file that gets `AGENTS.md` into a Claude Code session's context at
-   all, a separate baseline entry from `AGENTS.md` itself, so carrying one without the other
-   still leaves that provider unconfigured. **Before touching `AGENTS.md`, `GOVERNANCE.md`,
-   `CODESTYLE.md`, or `WORKFLOW.md` in this step, run the `carried-instruction-file-guard`
-   skill's distinctive-phrase probe against the target file, every time, without exception,
-   regardless of whether the update is a verbatim re-vendor or an intent-fidelity edit.** This is not advisory language to weigh against how routine
-   the diff looks, a diff that looks routine is exactly the shape the AGENTS.md-overwrite
-   incident took. Do not proceed to the re-vendor until the probe has run and any local addition
-   it finds has a destination, per that skill's own procedure. `CLAUDE.md` is outside that
-   guard's scope: it carries no mixed or repo-specific content by design, so its re-vendor is an
-   ordinary verbatim-fidelity copy, no probe needed.
+1. **The instruction set first.** `CLAUDE.md`, then `AGENTS.md` and `GOVERNANCE.md` verbatim sections, then `CODESTYLE.md` and `WORKFLOW.md`, including the `AGENTS.md` skill-dependency pointer paragraph (naming `scripts/skills_install.py` and where the fleet's Skills live) as one more verbatim unit carried in this same step, not a separate pass. `CLAUDE.md` is the single `@AGENTS.md`-import file that gets `AGENTS.md` into a Claude Code session's context at all, a separate baseline entry from `AGENTS.md` itself, so carrying one without the other still leaves that provider unconfigured. **Before touching `AGENTS.md`, `GOVERNANCE.md`, `CODESTYLE.md`, or `WORKFLOW.md` in this step, run the `carried-instruction-file-guard` skill's distinctive-phrase probe against the target file, every time, without exception, regardless of whether the update is a verbatim re-vendor or an intent-fidelity edit.** This is not advisory language to weigh against how routine the diff looks, a diff that looks routine is exactly the shape the AGENTS.md-overwrite incident took. Do not proceed to the re-vendor until the probe has run and any local addition it finds has a destination, per that skill's own procedure. `CLAUDE.md` is outside that guard's scope: it carries no mixed or repo-specific content by design, so its re-vendor is an ordinary verbatim-fidelity copy, no probe needed.
 2. **Deletions second, before any re-vendor.** Only a `retire` disposition in
    `spec/divergences.json` authorizes removing a file, and the removal is swept tree-wide, per
    RESYNC.md section 4, before the deletion counts as done.

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-79146733e388bff5
+69764939de16d10d

.claude-plugin/fleet-skills/skills/resync-a-repo/SKILL.md

@@ -49,21 +49,7 @@ Preserve the evidence RESYNC.md section 2 requires, and do not leave the finding
 
 ## Apply, in this order
 
-1. **The instruction set first.** `CLAUDE.md`, then `AGENTS.md` and `GOVERNANCE.md` verbatim
-   sections, then `CODESTYLE.md` and `WORKFLOW.md`, including the `AGENTS.md` skill-dependency
-   pointer paragraph (naming `scripts/skills_install.py` and where the fleet's Skills live) as
-   one more verbatim unit carried in this same step, not a separate pass. `CLAUDE.md` is the
-   single `@AGENTS.md`-import file that gets `AGENTS.md` into a Claude Code session's context at
-   all, a separate baseline entry from `AGENTS.md` itself, so carrying one without the other
-   still leaves that provider unconfigured. **Before touching `AGENTS.md`, `GOVERNANCE.md`,
-   `CODESTYLE.md`, or `WORKFLOW.md` in this step, run the `carried-instruction-file-guard`
-   skill's distinctive-phrase probe against the target file, every time, without exception,
-   regardless of whether the update is a verbatim re-vendor or an intent-fidelity edit.** This is not advisory language to weigh against how routine
-   the diff looks, a diff that looks routine is exactly the shape the AGENTS.md-overwrite
-   incident took. Do not proceed to the re-vendor until the probe has run and any local addition
-   it finds has a destination, per that skill's own procedure. `CLAUDE.md` is outside that
-   guard's scope: it carries no mixed or repo-specific content by design, so its re-vendor is an
-   ordinary verbatim-fidelity copy, no probe needed.
+1. **The instruction set first.** `CLAUDE.md`, then `AGENTS.md` and `GOVERNANCE.md` verbatim sections, then `CODESTYLE.md` and `WORKFLOW.md`, including the `AGENTS.md` skill-dependency pointer paragraph (naming `scripts/skills_install.py` and where the fleet's Skills live) as one more verbatim unit carried in this same step, not a separate pass. `CLAUDE.md` is the single `@AGENTS.md`-import file that gets `AGENTS.md` into a Claude Code session's context at all, a separate baseline entry from `AGENTS.md` itself, so carrying one without the other still leaves that provider unconfigured. **Before touching `AGENTS.md`, `GOVERNANCE.md`, `CODESTYLE.md`, or `WORKFLOW.md` in this step, run the `carried-instruction-file-guard` skill's distinctive-phrase probe against the target file, every time, without exception, regardless of whether the update is a verbatim re-vendor or an intent-fidelity edit.** This is not advisory language to weigh against how routine the diff looks, a diff that looks routine is exactly the shape the AGENTS.md-overwrite incident took. Do not proceed to the re-vendor until the probe has run and any local addition it finds has a destination, per that skill's own procedure. `CLAUDE.md` is outside that guard's scope: it carries no mixed or repo-specific content by design, so its re-vendor is an ordinary verbatim-fidelity copy, no probe needed.
 2. **Deletions second, before any re-vendor.** Only a `retire` disposition in
    `spec/divergences.json` authorizes removing a file, and the removal is swept tree-wide, per
    RESYNC.md section 4, before the deletion counts as done.

.github/skills/resync-a-repo/SKILL.md

@@ -49,21 +49,7 @@ Preserve the evidence RESYNC.md section 2 requires, and do not leave the finding
 
 ## Apply, in this order
 
-1. **The instruction set first.** `CLAUDE.md`, then `AGENTS.md` and `GOVERNANCE.md` verbatim
-   sections, then `CODESTYLE.md` and `WORKFLOW.md`, including the `AGENTS.md` skill-dependency
-   pointer paragraph (naming `scripts/skills_install.py` and where the fleet's Skills live) as
-   one more verbatim unit carried in this same step, not a separate pass. `CLAUDE.md` is the
-   single `@AGENTS.md`-import file that gets `AGENTS.md` into a Claude Code session's context at
-   all, a separate baseline entry from `AGENTS.md` itself, so carrying one without the other
-   still leaves that provider unconfigured. **Before touching `AGENTS.md`, `GOVERNANCE.md`,
-   `CODESTYLE.md`, or `WORKFLOW.md` in this step, run the `carried-instruction-file-guard`
-   skill's distinctive-phrase probe against the target file, every time, without exception,
-   regardless of whether the update is a verbatim re-vendor or an intent-fidelity edit.** This is not advisory language to weigh against how routine
-   the diff looks, a diff that looks routine is exactly the shape the AGENTS.md-overwrite
-   incident took. Do not proceed to the re-vendor until the probe has run and any local addition
-   it finds has a destination, per that skill's own procedure. `CLAUDE.md` is outside that
-   guard's scope: it carries no mixed or repo-specific content by design, so its re-vendor is an
-   ordinary verbatim-fidelity copy, no probe needed.
+1. **The instruction set first.** `CLAUDE.md`, then `AGENTS.md` and `GOVERNANCE.md` verbatim sections, then `CODESTYLE.md` and `WORKFLOW.md`, including the `AGENTS.md` skill-dependency pointer paragraph (naming `scripts/skills_install.py` and where the fleet's Skills live) as one more verbatim unit carried in this same step, not a separate pass. `CLAUDE.md` is the single `@AGENTS.md`-import file that gets `AGENTS.md` into a Claude Code session's context at all, a separate baseline entry from `AGENTS.md` itself, so carrying one without the other still leaves that provider unconfigured. **Before touching `AGENTS.md`, `GOVERNANCE.md`, `CODESTYLE.md`, or `WORKFLOW.md` in this step, run the `carried-instruction-file-guard` skill's distinctive-phrase probe against the target file, every time, without exception, regardless of whether the update is a verbatim re-vendor or an intent-fidelity edit.** This is not advisory language to weigh against how routine the diff looks, a diff that looks routine is exactly the shape the AGENTS.md-overwrite incident took. Do not proceed to the re-vendor until the probe has run and any local addition it finds has a destination, per that skill's own procedure. `CLAUDE.md` is outside that guard's scope: it carries no mixed or repo-specific content by design, so its re-vendor is an ordinary verbatim-fidelity copy, no probe needed.
 2. **Deletions second, before any re-vendor.** Only a `retire` disposition in
    `spec/divergences.json` authorizes removing a file, and the removal is swept tree-wide, per
    RESYNC.md section 4, before the deletion counts as done.

CLAUDE.md

@@ -2,6 +2,4 @@
 
 @AGENTS.md
 
-Claude Code reads `CLAUDE.md`, not `AGENTS.md`, so the import line above is what gets this
-repository's rules into a Claude Code session at all. See `AGENTS.md` for what is authoritative
-and why. This file carries no rule of its own, and adds none beyond the import line.
+Claude Code reads `CLAUDE.md`, not `AGENTS.md`, so the import line above is what gets this repository's rules into a Claude Code session at all. See `AGENTS.md` for what is authoritative and why. This file carries no rule of its own, and adds none beyond the import line.