2026-08-03 — Add default_branch to the mary-wiki registry entry
rank: decision outranks: []
Section titled “rank: decision outranks: []”2026-08-03 — Add default_branch to the mary-wiki registry entry
Section titled “2026-08-03 — Add default_branch to the mary-wiki registry entry”Date: 2026-08-03 Status: proposed Verb: request_review Slug: mary-wiki MR-compliance: MR-12
Rationale
Section titled “Rationale”The mary-wiki entry was seeded from the placeholder precedents (thrustr-io,
downlink-hq, pwplz — registry.yaml:705-740), which omit default_branch
because they have no repository to name a branch on. registry.schema.json
does not require the field.
pr-emitter.ts reads repoEntry.default_branch with no fallback to
main, so once the repo existed and the App was installed, every write verb
against mary-wiki still failed:
BASE_BRANCH_MISSING default_branch 'undefined' not found on mary-wiki/marymary-wiki/mary reports default_branch: main via the GitHub API.
Why request_review and not petrova_act_registry_edit
Section titled “Why request_review and not petrova_act_registry_edit”petrova_act_registry_edit emits a deterministic ADR path
(adrPath(date, verb, slug)). For today + this verb + this slug that path is
already on main from PR #200. The emitter refuses to overwrite it
(FILE_ALREADY_EXISTS, pr-emitter.ts:153-155) rather than silently rewriting
a merged decision doc, which would violate MR-7. The verb exposes an
adr_path override in its TypeScript options but not in its input schema, so
it cannot be redirected. request_review lets the caller name both paths.
Latent control-plane gap: two petrova_act_registry_edit calls against
the same slug on the same day always collide. Filed as a finding.
Sign-off
Section titled “Sign-off”Human merge required per MR-12 — opened with the awaiting-human-merge label.