Skip to content

Fleet naming completion: retire agent-sync naming in docs - #349

Merged
swu-wise[bot] merged 2 commits into
mainfrom
wise/fleet-naming-purge
Nov 2, 2026
Merged

swu-wise[bot] merged 2 commits into
mainfrom
wise/fleet-naming-purge

Conversation

@jaywedgeworth22

@jaywedgeworth22 jaywedgeworth22 commented Nov 2, 2026 •

Copy link
Copy Markdown
Member

Retires remaining agent-sync naming in agent-facing docs to complete the fleet naming migration. Coordination now points to #Work-In-Progress as the live channel and FLEET-PROTOCOL.md as the canonical protocol.

Changes:

  • AGENTS.md: replaces the agent-sync channel prohibition with a retired-channel guard directing agents to #Work-In-Progress.
  • EFFORT-LOG.md and docs/EFFORT-LOG.md: replaces historical AGENT-SYNC.md and #agent-sync references with FLEET-PROTOCOL.md, #Work-In-Progress, or generic fleet coordination wording.

Impact is docs-only with no application code change. User-visible effect is updated agent coordination guidance, while historical effort-log entries are reworded to the new names.

Testing: no tests were added and no test run is reported for this change in the diff. Test counts quoted inside the edited log entries are historical context only and remain unverified for this change.

Open risks from automated review, 3 medium and unresolved: guard in AGENTS.md states the retired channel does not exist while a stub may still exist. EFFORT-LOG.md and mirrored docs/EFFORT-LOG.md rewrite pre-cutover history to new channel names, which may affect audit accuracy. Correct handling of the stub and historical naming is unverified.

@kody-ai

kody-ai Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

⚠️ 1 Kody Rule(s) were not evaluated

These rules declare that they need repository context beyond this diff, and the review could not retrieve it, so they were not judged on this pull request:

  • Never log tokens or credentials; only safeIssues may reach the handoff file
Kody Guide: Usage and Configuration
Interacting with Kody
  • Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

  • Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug ✅
Performance ✅
Security ✅
Business Logic ✅

Access your configuration settings here.

​

Comment thread AGENTS.md Resolved
Comment thread EFFORT-LOG.md Resolved
Comment thread docs/EFFORT-LOG.md Resolved
@swu-wise

swu-wise Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Qualification update: fixed all three real review concerns in 8fb234b without restoring names the owner asked removed. The retired-channel nonexistence claim is gone, guard remains. Dated effort-log entries use generic channel/protocol wording instead of claiming newer names existed then; original dates, thread IDs and results remain. Three threads resolved with source fixes. Changes stay docs-only; current macOS CI pending, historical test counts in log are not this PR test evidence.

@swu-wise
swu-wise Bot merged commit 5d4f3a1 into main Nov 2, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant