docs(agnote): record the MAI-UI serving lane + correct the crawl-gap read

[POWERFULMOVES]

What

One CLAIM entry in the Active Claim Register for the crawl-gap lane. Docs only, 17 lines, no code.

This branch was pushed on 2026-08-07 and never got a PR — landing it so the lane is on the board rather than sitting unclaimed on origin. Claiming up front is the point: the register already records a prior lane that ran unclaimed and collided with Mavis.

The gap it records

Agent Zero (MC) has no fetch or crawl tool — its MCP registry is geometry.*, ingest.youtube, media.transcribe, comfy.render, notebook.search, form.get/switch. By design it calls Archon (Master DJ) for research.

Archon's half of that contract is real: archon.crawl.request.v1 / archon.crawl.result.v1 are registered in topics.json with closed schemas, the ARCHON JetStream stream is live (#2397, verified on 5090), and the dispatcher _handle_crawl_request → _process_crawl exists (restored in #2464, 39/39 tests green).

_process_crawl does not crawl. Re-verified against origin/main today:

crawl_result = {
    "status": "completed",
    "fragments": metadata.get("fragments", []),
    "extracted_text": metadata.get("extracted_text"),
}

It reads those two fields out of the incoming request metadata and republishes them as the result with status: "completed". There is no crawler anywhere in the repo — zero crawl4ai / firecrawl / scrapy in any Python file; the only textual hits are an archived AGNOTE and an audit dashboard.

So a crawl request returns an empty result and reports success. That is the same silent-success class this session has been correcting elsewhere.

Status since the claim was written

The entry's bounded work items (1) compose home for mai-ui-agent/Dockerfile, (2) MAI_UI_BACKEND=local|remote switch, (3) CUDA guard — are all implemented in #2468, which is open and awaiting Archon review. The claim text is left at its original 2026-08-07T02:00Z wording because it is a dated register entry, not a status page; the RELEASE belongs on #2468 when it merges.

Wiring _process_crawl to anything is explicitly out of this lane — operator sequencing is stabilize before wiring.

Risk

Zero. Single append to AGNOTE4482PHI.t1.md, no RELEASE line, no other agent's lane touched.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 16 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c36f7d29-babd-414e-a568-ec93a619753c

📥 Commits

Reviewing files that changed from the base of the PR and between 94cb6cf and 6c69632.

📒 Files selected for processing (1)

• pmoves/docs/AGENTS/AGNOTE4482PHI.t1.md

---

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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d1a441e56b

ℹ️ 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".

[POWERFULMOVES]

Field verification of #2479 — triggering a pull_request_review event now that the inline-mint fix is on main. Expect collect to get past checkout for the first time.

[POWERFULMOVES]

Field verification pass 3 for #2479 — this branch is now rebased onto main, so the head carries the inline-mint workflow. pull_request_review resolves the workflow from the PR head, which is why the first two attempts still ran the old file.