feat(zotero): emit reversible write execution receipts - #15
Conversation
…te-plan' into autoresearch/zotero-write-execution-receipt # Conflicts: # docs/product-technical-gap-baseline.md
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@codex review |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
@coderabbitai review |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 585f383bfc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…rch/zotero-write-execution-receipt
|
@coderabbitai review |
|
@codex review |
❌ Action failedReview failed.
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
@codex review |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Non-force two-parent restack onto current reviewed write-plan parent. Preserve the receipt/execution repairs while inheriting the repaired Foundation CI contract through the dependency chain. Signed-off-by: Seongho Bae <me@seonghobae.me>
|
Current-stack correction (2026-09-05): exact base |
Signed-off-by: Seongho Bae <me@seonghobae.me>
Current source-integrity note — 2026-09-05
autoresearch/zotero-write-execution-receipt@4ae166c501c83f6508011bcd31526815b69dd391.autoresearch/zotero-reviewed-write-plan@e35f42e2a552ba8da26250bf084462a36d1c986d.e7d4e59f1b55b5954c5f8436527bc96e7ef2fb13through ordinary merge ancestry. The source-snapshot digest binds complete captured raw provider JSON and the actual typed classifier inputs; source evidence and derived proposals retain separate identities.GoldenSetApproval.proposal_digestis required and binds the complete proposal records used for evaluation. The current proposal digest is checked before the caller-owned governance verifier. Do not backfill old receipts: regenerate evidence and obtain a new approval bound to the reviewed evidence.Earlier heads, runtime snapshots, campaign counts, and verification statements below are historical notes, not current acceptance evidence.
Historical PR notes — original text retained
Outcome
Provide the deterministic Zotero write-execution receipt boundary without claiming a live mutation. Complete reviewed-plan preflight precedes the first write; identity and full collection/tag state are verified around adapter calls; secret-free applied/failed/untouched evidence and reverse rollback operations are retained.
Current exact stack — 2026-09-05
821b04c640e798d851a21d893f9aa3d7d157470c;64cb10f817dbcd26f488f97dc63968fc7bf00af5;Repaired receipt invariants
ClassificationWriteReceiptis bound to review, authority, server, Zotero version, library version, rule revision and snapshot digest across DryRun, Applied, PreflightFailure and PartialFailure. DryRun performs no adapter calls and enumerates every plan operation as not attempted. Confirmed unexpected mutation retains inverse evidence only when server/item identity remains proven; identity drift does not fabricate rollback evidence. Execution-critical plan fields remain private with read-only accessors.Credentials remain outside serializable plans/receipts. Writes replace only complete reviewed collection/tag state for top-level items; complete preflight precedes mutation, later failure stops subsequent writes, and rollback operations remain reverse ordered.
Merge gate
Keep Draft behind #13 and the complete Foundation/Zotero prerequisite stack. Require one unchanged exact head with terminal Product/security/SAST/dependency/review evidence before integration. No self-approval, admin bypass, force-push, destructive rebase, predecessor-evidence transfer, or live mutation claim.
Refs #8.