docs: retain ci-fleet project name

[Nickfost]

Decision

Retain ci-fleet.

The accepted-decision record evaluates the requested names against the implemented trust boundaries, migration cost, search ambiguity, and current GitHub availability. ci-fleet accurately names the mature ephemeral-worker subsystem; tester and deployer roles intentionally remain separate and are not production-ready. Renaming now would imply unsafe integration and create migration churn without operating benefit.

The record includes explicit reconsideration triggers, a staged migration/compatibility plan, and rollback if a future ADR approves a rename. This PR renames nothing.

Evidence

• candidate availability checked in the RandomDevelopment namespace
• GitHub name search found no exact build-test-deploy-fleet or software-delivery-fleet; delivery-fleet is ambiguous with logistics projects
• python3 scripts/check_doc_links.py
• exact-commit committed-secret scan
• git diff --check

Closes #25.

[Nickfost]

@codex review

Focused exact-head review at f15e002. Verify that the decision satisfies #25 without implying any rename or external mutation, and that the rationale, alternatives, reconsideration trigger, staged migration scope, compatibility period, and rollback plan are complete and internally consistent.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: f15e00277a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".