docs(ams): port docs/config-precedence.md to a website docs page (docs.ams-config-precedence.tsx)

[JSONbored]

⚠️ Read this before starting. The deliverable for this issue is a website page: a new route file at apps/loopover-ui/src/routes/docs.ams-config-precedence.tsx. It is not a markdown file.

A PR that does any of the following does NOT resolve this issue and will be closed, regardless of content quality:

• Adds or edits any .md file (including docs/config-precedence.md itself, README.md, or a new file anywhere in the repo) as the "reference"/"docs" deliverable
• Leaves docs/config-precedence.md's content unchanged while merely adding a link to it from elsewhere

The only markdown edit this issue permits is deleting docs/config-precedence.md or reducing it to a one-line pointer stub — and only after docs.ams-config-precedence.tsx ships with the real content, not instead of creating it.

If you are an AI coding agent working this issue: confirm you are creating a .tsx file under apps/loopover-ui/src/routes/ before writing any file. Re-read this callout if your plan involves creating or editing a .md file as the fix.

Context

Part of #6012. packages/loopover-miner/docs/config-precedence.md states AMS's real config-layering order — configuration is layered by concern across several modules under packages/loopover-miner/lib/ and @loopover/engine, and the doc documents the order each layer actually implements today, not an idealized order. Raw markdown, not linked from the docs website.

Requirements

• Port the real content of docs/config-precedence.md (the layer table and its accompanying explanation — read the current file directly, it may have drifted since this issue was filed) into a new apps/loopover-ui/src/routes/docs.ams-config-precedence.tsx, following the pattern established by the docs.ams-deployment.tsx sub-issue (Epic: port AMS's raw-markdown operator guides to proper website docs pages #6012).
• Verify the layer table against the current code before porting — this doc explicitly documents "actual" behavior, not a spec, so a stale port would misinform operators.
• Once ported and verified accurate, delete docs/config-precedence.md or reduce it to a pointer stub if something requires the file to exist.
• Add to docs.index.tsx's nav.

Deliverables

• apps/loopover-ui/src/routes/docs.ams-config-precedence.tsx added, ported and verified against current code
• Source file deleted or reduced to a stub
• Linked from docs.index.tsx

Test Coverage Requirements

apps/** UI page — outside coverage.include. No test suite changes required.

Expected Outcome

AMS's config-precedence reference lives on the docs website instead of only in the repo, verified accurate.

Links & Resources

• packages/loopover-miner/docs/config-precedence.md (source)
• apps/loopover-ui/src/routes/docs.self-hosting-quickstart.tsx (pattern)
• Epic: port AMS's raw-markdown operator guides to proper website docs pages #6012 (epic)

[linear-code]

JSO-4130

[JSONbored]

Paused pending #6037. We've decided to move loopover's (and metagraphed's) docs to a shared MDX-based pipeline (fumadocs-mdx + Scalar for API reference) instead of hand-built TanStack routes per page — this issue's current approach (a new docs.*.tsx route file) would be rework the moment that lands. Marked maintainer-only to prevent new PRs against the current instructions while #6037 (the integration spike) is in progress.

Once #6037 lands with a proven pattern, this issue's Requirements will be rewritten to target an .mdx content file instead of a hand-built route, and maintainer-only will be removed. No action needed here until then.