docs(workorder): close out archon + NATS-auth lanes (Lane 1 done, Lane 2 non-urgent)

[POWERFULMOVES]

Closes the 2026-06-01 SPARK KIMI handoff work-order

Lane 1 — Archon fork-sync: DONE. Fork synced to upstream coleam00/Archon main (0.4.1), customizations preserved, oven/bun:1.3.14-slim base, Archon #15 merged, parent gitlinks reconciled #1674, vendored pin retired, fork branch-protection right-sized for solo operator.

Lane 2 — NATS-auth: scoped → non-urgent (no edit sweep). A scope-and-report pass (per the "check if already fixed first" rule the user set for Lane A) overturned the handoff's "~17 urgent files":

Surface	Finding	Verdict
env.shared.example:30	NATS_URL=nats://nats:pmoves@nats:4222	pipeline emits authed form
all prod wiring	os.getenv("NATS_URL", …) first; 0 consumers of bare constant	env wins → already authed
DoX config/system/chit_service	already normalizes both forms	done (#1375/#1292)
pmoves_health :4222	__main__ example block	cosmetic
announcer fallback / registry constant	unreachable / 0 consumers	defense-in-depth nit
~30 triple copies	md5 differs (drifted, not synced)	no clean single-source fix

Decision: no 30-file :4222→pmoves@:4222 sweep across hardened branches — pure churn for a non-issue. Any fallback hardening is a separate low-priority refactor at the canonical pmoves-cipher-mcp package, not a security patch.

Doc-only. Pairs with #1689 (base-image USER pattern from the same Lane-A pass).

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@POWERFULMOVES, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 10 minutes and 35 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7a2e649c-196e-4bd9-add8-404217b0f523

📥 Commits

Reviewing files that changed from the base of the PR and between f15ce9b and a65d893.

📒 Files selected for processing (1)

• pmoves/docs/handoffs/WORKORDER-archon-fork-sync-and-nats-auth-2026-06-01.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/workorder-laneb-closeout

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}