chore(guide): rename the agent-facing server to lore [release:v0.10.4]

[tcballard]

Summary

Settles the agent-facing server identity ahead of the MCP registry submission: the server is lore, matching the product name, on every surface an agent or user reads.

Adds:

• ADR-039 (Accepted): the agent-facing identity — client config label, server handshake name, registry name — is lore. Everything ADR-036 froze stays frozen: the rac mcp command, the rac CLI, the requirements-as-code package, and all tool names, descriptions, and response contracts. lore-guide is recorded as rejected (it would create a third name when the problem was having two); "Guide" remains the internal component name in code, tests, and corpus.
• The rename itself: SERVER_NAME = "lore" in src/rac/mcp/server.py, plus every documented config block — README, docs/mcp.md, examples/guide/demo.md, the session-start prompt, and this repo's own .mcp.json. Zero rac-guide occurrences remain.
• Registry submission assets: server.json at the repo root declaring io.github.tcballard/lore (PyPI package, stdio transport, v0.10.4), and the mcp-name: io.github.tcballard/lore ownership marker as an invisible HTML comment at the top of the README — the marker PyPI ownership validation requires once a release carries it.

Roadmap / ADR Trace

Decisions:

• rac/decisions/adr-039-lore-server-identity.md (new, Accepted)
• rac/decisions/adr-036-lore-product-identity.md — scoped against explicitly; its distribution-name freeze holds
• rac/decisions/adr-029-guide-delivery-surface.md — delivery mechanics unchanged

Roadmap: completes the registry-submission preparation from v0.10.2-guide-grounding-demo.md Initiative 5 (the submission itself is a human step).

Scope

Included

• Label-level rename only: handshake name, config keys, docs, registry manifest, ownership marker

Excluded

• No tool surface, contract, CLI, or package changes; no behavior changes of any kind (the suite passes untouched — no test pinned the old label)
• The registry publish itself (mcp-publisher login github then mcp-publisher publish is a maintainer device-flow step, after the v0.10.4 release puts the marker on PyPI)
• A uvx runtime hint in server.json (deferred per ADR-029; revisit if mcp-publisher validation suggests it)

Verification

python -m pytest -q                    # 934 passed, untouched by the rename
python -m ruff check src/ tests/      # clean
python -m mypy src/                    # no issues
rac validate rac/                      # 104 valid, 0 invalid
rac relationships rac/ --validate      # 0 issues
rac review rac/                        # no priority 1-2 findings
python -c "import json; json.load(open('server.json'))"
grep -rn "rac-guide" src/ tests/ docs/ examples/ README.md .mcp.json   # no matches

The renamed server was exercised live in an agent session via the project .mcp.json (get_artifact retrieved ADR-036 through the running server while this decision was being made).

Review Path

1. rac/decisions/adr-039-lore-server-identity.md — the decision and its scope boundary against ADR-036
2. src/rac/mcp/server.py — the one-line handshake rename
3. README.md, docs/mcp.md, examples/guide/demo.md, .mcp.json, rac/prompts/rac-agent-session-start.md — config blocks
4. server.json — the registry manifest

Notes For Reviewer

• Sequencing after merge: tag v0.10.4 and publish the Release (PyPI then carries both the ownership marker and the banner-rendering fix from the previous PR), then mcp-publisher publish. Registry validation fails until the marker is live on PyPI.
• v0.10.3's published docs show rac-guide; anyone who configured that label keeps a working server under the old name until they re-add it — noted in ADR-039's consequences.

Implementation Process

Implemented with AI assistance under the roadmap contract. Final scope, review, and acceptance decisions were made by the maintainer.