Add Fleet Map and Gap Register, Declare Peer Messaging - #687
Merged
Conversation
The skill-based fleet system has defined procedures but undefined seams: the skills install has no home in the cold-start flow, a failed tool floor names no remedy, and several topics carry no skill. docs/fleet-map.md maps every entry point, registers twelve gaps with a handoff and a closing test each, resolves the install model as global with its gaps enumerated, proposes four skills, and phases the closure work. docs/peer-messaging.md resolves the TODO.md location decision by declaring the live method and its safety rules hub-only until cross-host is verified.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds hub-only documentation to make the skill-based fleet system's entry points and coordination seams explicit, and updates the hub TODO backlog to point to the new gap register and peer-messaging standard.
Changes:
- Add
docs/fleet-map.mdto map fleet entry points, define a gap register (G1-G12), and outline proposed skills and closure phases. - Add
docs/peer-messaging.mdto declare same-host agent-to-agent messaging and its safety rules, with promotion criteria. - Update
TODO.mdto point fleet adoption gaps to the new register and mark the peer-messaging cluster as ready/settled with references to the new docs.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| TODO.md | Adds a pointer to the fleet gap register and resolves/settles the peer-messaging backlog cluster to the new hub-only doc. |
| docs/peer-messaging.md | Introduces the hub-only peer-messaging method, safety rules, and promotion criteria with reference links. |
| docs/fleet-map.md | Introduces the hub-only fleet map, gap register, proposed-skill inventory, and phased closure roadmap with references. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
ptr727
added a commit
that referenced
this pull request
Aug 15, 2026
…Python CI Gates (#718) Thirty-one squashes, `56f4d7d..d54862a`. 115 files, +20436/-5298. **Merge with a merge commit, never a squash, and never with `--delete-branch`.** This pull request's head is `develop` itself. ## What lands **Fleet Skills.** The `.agents/skills/` source tree, the generated `.claude-plugin/` distribution, `scripts/build_dist.py` with its `--check` gate, and `scripts/skills_install.py` with its host stamp (#676). Packaged as skills on top of the scaffold: PR review conduct and Copilot instructions upkeep (#677), comment and doc style (#678), resync-a-repo and fleet-conformance-check (#679), the per-language codestyles (#680), git commit conventions and operational vs release workflow (#681), stand up a repo (#683), and repo-worktree (#717). Coverage gaps closed in three passes (#690, #691, #692) plus the P4 sentence-length opt-in (#697). **Host setup.** The Windows host-setup tooling and its PowerShell gate (#674), the Windows bootstrap loader (#682), Docker install and upgrade on Linux and Windows with a version floor (#701, #705), a `uv` floor in `spec/host-tools.json` (#698), self-healing of a shadowing `uv`, `jq`, or `git-restore-mtime` copy (#689), node's real winget package id (#696), and a README for the Linux host-setup nuances (#710). **Python and CI.** Python tooling in CI with the script tests moved to `scripts/tests` (#704), `ruff format` adopted and gated (#709), and the PSScriptAnalyzer claim conditioned on repos that carry `.ps1` files (#686). **Conduct rules.** Triage-order and scope guardrails in pr-review-conduct (#684), `pr_review.py wait` requesting a review rather than only polling for one (#685), a tech-agnostic signed-commit verification (#708), execution rather than analogy to verify platform-specific code (#715), and a unique worktree for every task (#717). **Docs.** The fleet map and gap register with peer messaging declared (#687), mermaid flow diagrams in the kept-authority docs (#702), and the map pointed at the shipped diagrams and current tooling (#703). ## Issues this promotion closes Each landed on `develop` on its own pull request. The keyword fires only on a merge into `main`, so it sits here rather than on the feature pull requests. Closes #700 Closes #707 Closes #711 Closes #712 Closes #714 Closes #688 #699 stays open on purpose: #717 shipped the layout convention and the skill, and the physical migration of existing checkouts is still tracked there. ## Review record Every squash closed its own Copilot loop on its own pull request before merging to `develop`. This promotion carries no new content of its own, so its review is the merged tree as a whole. ## Consequence worth stating The `GOVERNANCE.md` and `AGENTS.md` sections these squashes changed become the canonical the moment this reaches `main`, and every carrying repository reads as drifted from that point until it resyncs. That is the ordinary consequence of a canonical moving rather than a defect. The Skills installer added here is also how a machine picks the new skills up, so a session that keeps restating a rule already packaged as a skill is the signal to run it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The skill-based fleet system has defined procedures but undefined seams between them. The skills install has no home in the cold-start flow, a failed tool floor names no install remedy, session entry never checks skill staleness, and WORKFLOW.md, AUDIT.md, and the conduct rules carry no skill. Each gap was real but recorded nowhere, so each session rediscovered them.
What
docs/fleet-map.md(hub-only): maps the five entry points into the fleet system with a flowchart each, registers twelve gaps (G1-G12) with a defined handoff and a closing test per gap, resolves the skills install model as global with its wiring gaps enumerated, proposes four new skills (audit-a-repo,workflow-ci-contract,skill-lifecycle,agent-conduct) with scope and overlap settled, evaluates ASD-STE100 against a constrained house style, and phases the closure work P0-P4. Carries its own maintenance rule: a PR closing a gap edits its register row in the same change.docs/peer-messaging.md(hub-only): declares the live agent-to-agent messaging method and its four safety rules, resolving the TODO.md location decision to a hub-only doc until cross-host is verified. Closes register gap G11.TODO.md: the peer-messaging cluster's two open bullets resolve by pointer to the new docs, and one added line establishes the fleet-map register as the home for adoption gaps so the two files do not fork.Verification
prose_lint.py --diff HEAD,repo_gate.py --check eol, andmarkdownlint-cli2all pass on the three files.flowchart-v2viamermaid.parse(mermaid 11).git ls-files --eol.Generated with Claude Code