rpg-aplicar-glosas

rpg-aplicar-glosas — Apply the pending Glosas queue

Run against the current vault (CWD must be the vault root). List the pending queue first. If the vault's MCP server is running (the mcp__rpg-vault__list_glosas tool is available in this session), call it instead with { status: "pendente" }: it answers from the server's live index in one call, with the same result. Otherwise, run the script:

node "${CLAUDE_PLUGIN_ROOT}/scripts/glosas.mjs" --vault "$(pwd)" --status pendente

If there are none, tell the GM the queue is empty and stop.

Otherwise work through the pending Glosas one at a time, in the order printed (oldest first). For each one, read its fields:

• alvo — one or more vault-relative note paths this Glosa concerns.
• tipo — entidade (a note on the whole Entity), trecho (a note on a quoted passage) or campo (a proposed new value for one field).
• campo/de/para (only for tipo: campo) — the field and its proposed new value.
• trecho (only for tipo: trecho) — the exact passage the Glosa points at.
• comentario — the GM's own words; always read this even when the other fields already say what to change, since it's often the reason, not just the instruction.

1. Apply the change to every target

Edit every note listed in alvo — never only the first — through the normal write path, exactly as you would for any other Entity change:

• tipo: campo — campo is the note's own frontmatter key (role, status, location, faction, front…): use rpg-preserve's "Updating an existing entity" recipe (a patch merging { [campo]: para } into the existing frontmatter; a link value such as [[O Mercado das Cinzas]] is already written the way the note stores it). Two values of campo are not frontmatter keys:
  • epiteto — the italic epithet line right under the title: replace that line's text (de) with para, through the same recipe's body rewrite.
  • titulo — the note's title. Change its # H1 to para the same way, then tell the GM the file itself still carries the old name: renaming it is the GM's call in Obsidian, which also updates every link to it.
• tipo: trecho — use the same recipe, replacing the quoted trecho within the body with the corrected text (build the new body yourself; the recipe carries the rest of the body through verbatim).
• tipo: entidade — use whichever recipe fits the comment: a field patch, a body addition (append), or a body rewrite.