Pablu/diple
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: resolve pending and jumping

Browse Source
This commit is contained in:
pablu
2026-08-03 13:31:45 +02:00
parent 4fcc479779
commit 6f963c7660
9 changed files with 330 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@@ -523,16 +523,19 @@ Cached data is labelled when first shown. A normal refresh does not repeatedly
reintroduce the cached header.
Read state and recoverable drafts live beside the configuration file as
`state.json` and `drafts.json`. Confirmed reversible GitHub writes are kept in
`mutation-queue.json` until GitHub confirms them. Experimental AI data defaults
`state.json` and `drafts.json`. Reversible GitHub writes are kept in
`mutation-queue.json` until a live refresh verifies them. Experimental AI data defaults
to the `ai` directory beside the configuration. These files are versioned and
written atomically; sensitive user-authored state uses restrictive permissions.
Cached permission gates are treated as the last known truth while offline:
actions granted by the snapshot can be queued, while actions denied by it stay
disabled. Pending replies and projected PR or thread changes are labelled in
the UI without being written into the read cache. Replay preserves global
enqueue order, including across repositories.
disabled. Queued replies and projected PR or thread changes are displayed
optimistically as successful without being written into the read cache. A
pending marker appears only after a live refresh cannot verify the change or a
definite rejection needs attention. Retryable transport failures remain
optimistic and are recorded in Health. Replay preserves global enqueue order,
including across repositories.
If GitHub permissions or the target changed, replay pauses before the first
unsafe operation and presents choices to keep it queued, discard that item and