⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.
Artifacts
Summary
Adopt ADR-063 ("MCP as Platform Abstraction") in Larpinq by declaring the
x-openregister-mcp schema dialect on a curated set of 9 register schemas
(character, player, setting, skill, item, condition, event,
xpAward, attendance), so OpenRegister derives MCP tools for Hermiq without
any hand-written provider code. Larpinq has no existing IMcpToolProvider,
so this is a pure dialect declaration (kind: config). Unlike the read-only
Software Catalog sibling change, three narrow write verbs are enabled
(character.create, xpAward.create, attendance.update) because a LARP
campaign is genuinely low-stakes and each write maps to a documented,
RBAC-gated, additive/lifecycle-bounded action a GM or player would plausibly
ask an assistant to perform.
Specs
Tasks
Design
See design.md for technical design details.
Synced from openspec/changes/larpinq-mcp-adoption by OpenSpec workflow
App: larpinq
Artifacts
Summary
Adopt ADR-063 ("MCP as Platform Abstraction") in Larpinq by declaring the
x-openregister-mcpschema dialect on a curated set of 9 register schemas(
character,player,setting,skill,item,condition,event,xpAward,attendance), so OpenRegister derives MCP tools for Hermiq withoutany hand-written provider code. Larpinq has no existing
IMcpToolProvider,so this is a pure dialect declaration (
kind: config). Unlike the read-onlySoftware Catalog sibling change, three narrow write verbs are enabled
(
character.create,xpAward.create,attendance.update) because a LARPcampaign is genuinely low-stakes and each write maps to a documented,
RBAC-gated, additive/lifecycle-bounded action a GM or player would plausibly
ask an assistant to perform.
Specs
Tasks
openspec validatepassesDesign
See design.md for technical design details.
Synced from
openspec/changes/larpinq-mcp-adoptionby OpenSpec workflowApp:
larpinq