[Madraka]

RFC-0038 / ADR-0040, step 3 of 3. Closes #50.

Studio

• A Collections section in Site settings (CollectionSettings.tsx, logic in lib/collection-permalinks.ts), gated on settings.write.
• Each row is a collection: the keys of site.collections plus the collections its entries use. The InputGroup holds the prefix before /{slug}, and the preview shows a real entry's address (and its old address once it changes, with a note that it redirects).
• Saving goes through PUT /api/sites/:id. Empty, or the collection's own name, means the default.
• Validated in the browser like the schema; a path_conflict / reserved_path 409 shows on that row.
• ConflictBanner moved to its own component (SiteSettingsPage 881 → 859 lines).
• English strings, plus drafts for the other 18 languages through .i18n + i18n:import. These are not marked reviewed.

MCP: set_collection_permalink { siteId, collection, permalink | null, dryRun? }

• Scope: the agent needs site:write.
• Approval: requiresApproval + classify: person, so it waits for a person in every mode, bypass included. dryRun: true is classified read and returns the plan only.
• Precheck before anyone is asked: the pattern, a no-op, and the store's checks via the new SiteGraphStore.updateSite(site, { dryRun: true }).
• The prompt lists the old and new template, the entry count, up to 3 entries with their old and new URLs, the redirect added and existing redirects repointed or dropped, and the locales.
• get_site documents collections; the server instructions and the README list the tool.

Who may approve (added in review)

New optional ToolPolicy.approverScopes (@cloudhal/agent-runtime), checked in the API's canDecide. This tool sets ["site:settings"]: the person approving must be able to change site settings, as in Studio, so an Editor cannot approve an agent's URL move. Person-only scopes can't be a tool's own scopes (they never satisfy a tool), which is why this is a separate field.

Other changes

• Menus: a collection's menu link goes to a published page at its permalink prefix first, then to the page that lists it.
• Starter: the README mentions collection permalinks.

Checks (one package at a time)

Package	Tests
api	379/379, incl. the new shared testing-permalinks.ts on sqlite + D1, and approver-scopes.test.ts
mcp-server	145/145 (e2e tool count 101 → 102)
Studio	1144/1144 (design rules, i18n)
core-ts	654/654
astro-renderer	257/257
agent-runtime	72/72

Also passing: typecheck, size ratchet (baseline tightened), design lint (340 files), i18n import checks.

Studio was checked through the API on a local server: /blog/{slug} gave rev 6 plus the 301, and /about/{slug} gave 409. It was not checked visually, because the local Studio needs a signed-in account.

Open questions (follow-ups)

1. A moved collection cannot have a page at its prefix (step 2), so its menu link falls back to the listing page. Wait for indexPath, or allow a page at the prefix itself?
2. The row error shows the catalog's generic conflict text, not the server's message naming the page or archive.

🤖 Generated with Claude Code