Artifact Description [91227a92e1]

Artifact 91227a92e1acf5d1845f79e43ee50ed87049d1d77c44d60d2864d6de05134177:

• File internal/api/register.go
  • 2026-08-26 15:45:04 — part of check-in [bda97ce3df] on branch protected-branches — landings: one write path for remarks again (zit#149)

    zit landing comment grew --reply-to, so a parented remark no longer has to detour through forum reply. Both cases go through LandingSay, which means the landing-specific error handling below — conflict and refusal decoding — now covers every remark rather than half of them.

    The same-thread check stays. zit refuses an out-of-thread target too, but here it is a capability boundary: quarry does not delegate its permission model to an upstream refusal.

    Verified the artifact cards are unchanged: G=root, I=parent, identical to what the forum-reply path produced. (user: dmestas, size: 274206) [annotate] [blame] [check-ins using]

  • 2026-08-26 15:46:47 — part of check-in [3886890ee7] on branch trunk — landings: one write path for remarks again (zit#149)

    zit landing comment grew --reply-to, so a parented remark no longer has to detour through forum reply. Both cases go through LandingSay, which means the landing-specific error handling below — conflict and refusal decoding — now covers every remark rather than half of them.

    The same-thread check stays. zit refuses an out-of-thread target too, but here it is a capability boundary: quarry does not delegate its permission model to an upstream refusal.

    Artifact cards verified unchanged: G=root, I=parent, identical to what the forum-reply path produced. (user: dmestas, size: 274206) [annotate] [blame] [check-ins using]