fix: verify live GitHub bodies and prepare v1.3.4

[Wibias]

Summary

• close the remaining live-body verification gap for comment/reply/review publications
• keep the canonical stdin/JSON body transport as the write path and fail closed when the authoritative GitHub body does not match
• reuse the canonical authenticated-actor lookup for collection fallback and keep forged-marker receipts from another actor non-authoritative
• prepare patch release 1.3.4 with the complete consumer-facing delta since v1.3.3 (fix: close off-mode trusted intent bypass #389, fix: fail closed on unresolved GraphQL mutation roots #390, fix: bind native approvals to the authorised head #391, and this fix)

Runtime fix

Body-bearing social mutations now re-read the authoritative GitHub object after a successful write. Direct receipt IDs are used when available; otherwise collection fallback requires the exact idempotency marker, the authenticated GitHub actor, and the reply parent where applicable. The postcondition then requires the live body to match the exact intended markdown.

The router deliberately gives postcondition verification the unfiltered body-safe runner rather than the receipt-filtered runner, so malformed live bodies cannot disappear from verification through idempotency filtering.

TDD / regression evidence

The initial test-only head was RED on the intended missing-live-reread behavior.

During GREEN work, the retained forged-actor regression exposed two compatibility assumptions rather than a reason to weaken the new invariant:

1. the postcondition initially introduced an incompatible JSON actor lookup; it now reuses the canonical readAuthenticatedActor() contract (gh api user --jq .login), and
2. the forged-marker fixture now models remote state across the write: before publication only the attacker record exists; after the real write the authenticated actor's exact published body is visible and must satisfy the new postcondition.

On the production/release path, the canonical Node 24 repository checks and Node 22 compatibility pass with the strengthened forged-actor and live-body regressions.

Release 1.3.4

Base release: v1.3.3 / 69884f3ea72e035c080547b076d907e077a33c3d

The release notes cover the complete consumer-facing delta since that tag:

• fix: close off-mode trusted intent bypass #389 — authorityMode=off is planning-only for GitHub writes; model-callable workflow flags/helper invocation cannot mint trusted remote-mutation intent.
• fix: fail closed on unresolved GraphQL mutation roots #390 — unresolved GraphQL mutation root selections, including fragment spreads and inline fragments, fail closed.
• fix: bind native approvals to the authorised head #391 — native approval is created for the exact expected head and post-verified against actor, commit, state, marker, plus a post-write head re-read.
• fix: verify live GitHub bodies and prepare v1.3.4 #392 — body-bearing social mutations require authoritative post-publication live-body verification.

package.json, README current-state/release notes, and CHANGELOG.md are prepared for 1.3.4.

Tag creation, GitHub Release publication, release assets, npm publication, and merge of this PR are not part of this PR and remain separately authorized.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 65bb280f-b3ed-46e6-8743-e135441c433a

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}