Cut WORKFLOW.md Section 2 to a Pointer at Workflow YAML Conventions

.agents/skills/workflow-ci-contract/SKILL.md

@@ -20,7 +20,7 @@ description: >-
 
 ## Style Rules
 
-`GOVERNANCE.md` "Workflow YAML Conventions" and `WORKFLOW.md` section 2 keep the style rules. Read both before editing a workflow or a composite action.
+`GOVERNANCE.md` "Workflow YAML Conventions" keeps the style rules, and the `comment-and-doc-style` Skill keeps the line-ending policy, reached from `GOVERNANCE.md` "Documentation Style Conventions" under "Line Endings". Read both before editing a workflow or a composite action.
 
 ## The Core Behavioral Spine
 

.agents/skills/workflow-ci-contract/references/d-guarantees.md

@@ -73,7 +73,7 @@ The required behaviors, organized by domain. Each is a **MUST**, stated as the o
 
 ### D9 - Style / Static
 
-`WORKFLOW.md` section 2 names the tool D9.1 excepts and states the suffix rules D9.2 requires.
+`GOVERNANCE.md` "Workflow YAML Conventions" names the tool D9.1 excepts and states the suffix rules D9.2 requires.
 
 - **D9.1** Every action SHA-pinned with a version comment (sole exception: the documented lagging-tag tool).
 - **D9.2** File/workflow/job/step names follow the suffix rules. A ruleset-bound job's `name:` equals its ruleset `context:` (renamed together).

.claude-plugin/fleet-skills/.source-digests/workflow-ci-contract

@@ -1 +1 @@
-7ac8da4fea70fd45
+f3440e45d74297ac

.claude-plugin/fleet-skills/skills/workflow-ci-contract/SKILL.md

@@ -20,7 +20,7 @@ description: >-
 
 ## Style Rules
 
-`GOVERNANCE.md` "Workflow YAML Conventions" and `WORKFLOW.md` section 2 keep the style rules. Read both before editing a workflow or a composite action.
+`GOVERNANCE.md` "Workflow YAML Conventions" keeps the style rules, and the `comment-and-doc-style` Skill keeps the line-ending policy, reached from `GOVERNANCE.md` "Documentation Style Conventions" under "Line Endings". Read both before editing a workflow or a composite action.
 
 ## The Core Behavioral Spine
 

.claude-plugin/fleet-skills/skills/workflow-ci-contract/references/d-guarantees.md

@@ -73,7 +73,7 @@ The required behaviors, organized by domain. Each is a **MUST**, stated as the o
 
 ### D9 - Style / Static
 
-`WORKFLOW.md` section 2 names the tool D9.1 excepts and states the suffix rules D9.2 requires.
+`GOVERNANCE.md` "Workflow YAML Conventions" names the tool D9.1 excepts and states the suffix rules D9.2 requires.
 
 - **D9.1** Every action SHA-pinned with a version comment (sole exception: the documented lagging-tag tool).
 - **D9.2** File/workflow/job/step names follow the suffix rules. A ruleset-bound job's `name:` equals its ruleset `context:` (renamed together).

.github/skills/workflow-ci-contract/SKILL.md

@@ -20,7 +20,7 @@ description: >-
 
 ## Style Rules
 
-`GOVERNANCE.md` "Workflow YAML Conventions" and `WORKFLOW.md` section 2 keep the style rules. Read both before editing a workflow or a composite action.
+`GOVERNANCE.md` "Workflow YAML Conventions" keeps the style rules, and the `comment-and-doc-style` Skill keeps the line-ending policy, reached from `GOVERNANCE.md` "Documentation Style Conventions" under "Line Endings". Read both before editing a workflow or a composite action.
 
 ## The Core Behavioral Spine
 

.github/skills/workflow-ci-contract/references/d-guarantees.md

@@ -73,7 +73,7 @@ The required behaviors, organized by domain. Each is a **MUST**, stated as the o
 
 ### D9 - Style / Static
 
-`WORKFLOW.md` section 2 names the tool D9.1 excepts and states the suffix rules D9.2 requires.
+`GOVERNANCE.md` "Workflow YAML Conventions" names the tool D9.1 excepts and states the suffix rules D9.2 requires.
 
 - **D9.1** Every action SHA-pinned with a version comment (sole exception: the documented lagging-tag tool).
 - **D9.2** File/workflow/job/step names follow the suffix rules. A ruleset-bound job's `name:` equals its ruleset `context:` (renamed together).

AGENTS.md

@@ -97,7 +97,7 @@ Every rule below is a level-two section of [`GOVERNANCE.md`](./GOVERNANCE.md) un
 | Opening a pull request, or requesting, monitoring, answering, or closing a review | `PR Review Etiquette`, packaged as the `pr-review-conduct` Skill |
 | Reviewing a pull request, patch, or change set | No section of its own: the `code-review` Skill, which routes to the applicable general, language, documentation, and workflow skills |
 | Reporting progress or asking the user something | `Communicating with the User`, surfaced at its decision moment by the `agent-conduct` Skill, and the section keeps the full rules |
-| Editing a workflow YAML file | `Workflow YAML Conventions`, surfaced with the full `WORKFLOW.md` contract by the `workflow-ci-contract` Skill, and this section and `WORKFLOW.md` keep the full rules |
+| Editing a workflow YAML file | `Workflow YAML Conventions`, surfaced with the full `WORKFLOW.md` contract by the `workflow-ci-contract` Skill, that section keeping the style rules and `WORKFLOW.md` the contract |
 | Choosing an OS, runtime, or toolchain target | `Supported Development Platforms` |
 | The devcontainer | `Devcontainer` |
 | Editor settings and tasks | `Editor and Tasks` |

GOVERNANCE.md

@@ -221,7 +221,7 @@ The provider-specific mechanics this contract needs to actually drive GitHub Cop
 
 These conventions describe the target state. New and modified workflows must respect them. The rest of the repo is expected to be brought up to the same standard. Sweep PRs that apply a rule everywhere are welcome when a rule changes.
 
-This section and [`WORKFLOW.md`](./WORKFLOW.md) keep the full rules, this section winning where the two overlap, and both are surfaced by the `workflow-ci-contract` Skill at `.agents/skills/workflow-ci-contract/SKILL.md` in the hub, not a repo-relative link since that path is hub-local and not carried into every fleet repo.
+This section keeps the full rules and wins where [`WORKFLOW.md`](./WORKFLOW.md) overlaps it, and `WORKFLOW.md` section 2 points at it rather than restating it. The `workflow-ci-contract` Skill at `.agents/skills/workflow-ci-contract/SKILL.md` in the hub, not a repo-relative link since that path is hub-local and not carried into every fleet repo, surfaces it.
 
 - **Action pinning**: pin **every** action, first-party (`actions/*`) and third-party alike, to a commit SHA with a trailing `# vX.Y.Z` comment, so Renovate / Dependabot can still bump it but a tag swap can't change the executed code. Use `# vX` (major-only) only when the upstream's floating major tag doesn't correspond to a specific patch/minor release SHA, since pinning to the floating-tag SHA still gives the SHA guarantee, the version comment just records the major line. Documented exception (no SHA pin at all): `dotnet/nbgv` is consumed via `@master` because the upstream tag stream lags `master` substantially and Dependabot's tag-tracking would propose a downgrade. **This applies to repo-owned build-layer leaves too**, since a leaf owning its build specifics is not a reason to use floating tags, and Dependabot still bumps SHA pins (updating the SHA + version comment).
 - **Filename**: reusable workflows (those with `on: workflow_call`) end in `-task.yml`. Entry-point workflows (`on: push` / `pull_request` / `schedule` / `workflow_dispatch`) do NOT use the `-task` suffix. They end with what they do: `-pull-request.yml`, `-release.yml`, etc. The suffix carries semantic meaning: a `-task.yml` file is meant to be `uses:`-d, never triggered directly.