Auth 0.1.17: continue publishing after a failed step (#4) #8

Merged
rhelwig merged 3 commits from fix/auth-continue-on-fail into main 2026-10-10 18:39:33 +00:00
Owner

Implements #4: continue publishing remaining writes after one item fails.

Engine (apps/android-auth/engine/release-execution.ts)

  • Item failures are recorded and the run continues: READ_UNAVAILABLE (still failing after the 0.1.16 read retries), OPERATION_CHANGED, SIGNING_FAILED (before any receipt is saved), and proven NETWORK_REJECTED (status ERROR + verified nonce consumption).
  • Still stops the run: an uncertain write (never rebroadcast), expiry, contract/key/nonce/protocol/credit changes, a changed site, receipt/outcome save failures.
  • Site activation is skipped (DEPENDENCIES_INCOMPLETE) while any dependency is missing, so the live site stays on the previous release.
  • Circuit breakers: 3 consecutive item failures (TOO_MANY_FAILURES), 2 rejections per run (REPEATED_REJECTIONS).
  • Result: {status, confirmed, failed, total, items[], stoppedBy?}; status values unchanged.

Auth app 0.1.17 (versionCode 18)

  • Progress line shows failed count; end-of-run card lists failed/skipped steps with fixed reasons.
  • Check again · retry N remaining steps re-plans only records still missing on Platform (new fee review + device approval).
  • Publication history shows the last run summary (journal lastRun, cleared on publish).

Tests

  • Failure injection in tests/release-execution.test.ts: read failure mid-batch + retry of only remaining steps, signing failure, changed operation, bad signed hash, global preflight abort, circuit breaker, inspection read failure, rejection-then-continue with exact nonces, uncertain still stops.
  • Updated engine/shared-destination tests; Kotlin PublicationSummaryTest + progress test.
  • npx tsx --test tests/*.test.ts: 165/165 pass. ./gradlew :protocol:test :app:compileDebugKotlin -PauthNetwork=mainnet: pass.

Docs: DECENTSITE-AUTH, SPECS, IMPLEMENTATION-PLAN, PUBLISH-FOLLOWUPS.

Closes #4 once merged and tested on device. No Dash spent.

Implements #4: continue publishing remaining writes after one item fails. **Engine (`apps/android-auth/engine/release-execution.ts`)** - Item failures are recorded and the run continues: `READ_UNAVAILABLE` (still failing after the 0.1.16 read retries), `OPERATION_CHANGED`, `SIGNING_FAILED` (before any receipt is saved), and proven `NETWORK_REJECTED` (status ERROR + verified nonce consumption). - Still stops the run: an uncertain write (never rebroadcast), expiry, contract/key/nonce/protocol/credit changes, a changed site, receipt/outcome save failures. - Site activation is skipped (`DEPENDENCIES_INCOMPLETE`) while any dependency is missing, so the live site stays on the previous release. - Circuit breakers: 3 consecutive item failures (`TOO_MANY_FAILURES`), 2 rejections per run (`REPEATED_REJECTIONS`). - Result: `{status, confirmed, failed, total, items[], stoppedBy?}`; `status` values unchanged. **Auth app 0.1.17 (versionCode 18)** - Progress line shows failed count; end-of-run card lists failed/skipped steps with fixed reasons. - **Check again · retry N remaining steps** re-plans only records still missing on Platform (new fee review + device approval). - Publication history shows the last run summary (journal `lastRun`, cleared on publish). **Tests** - Failure injection in `tests/release-execution.test.ts`: read failure mid-batch + retry of only remaining steps, signing failure, changed operation, bad signed hash, global preflight abort, circuit breaker, inspection read failure, rejection-then-continue with exact nonces, uncertain still stops. - Updated engine/shared-destination tests; Kotlin `PublicationSummaryTest` + progress test. - `npx tsx --test tests/*.test.ts`: 165/165 pass. `./gradlew :protocol:test :app:compileDebugKotlin -PauthNetwork=mainnet`: pass. Docs: DECENTSITE-AUTH, SPECS, IMPLEMENTATION-PLAN, PUBLISH-FOLLOWUPS. Closes #4 once merged and tested on device. No Dash spent.
Item failures (reads still failing after retries, changed operation,
signing failure before a receipt, proven network rejection) are recorded
and independent writes continue. Uncertain writes, expiry and global
invariant changes still stop the run; nothing is ever rebroadcast. Site
activation is skipped while a dependency is missing. Circuit breakers:
3 consecutive item failures, 2 rejections per run. Failure-injection
tests cover each path and retrying only the remaining steps.
PublicationSummary (fixed codes only), failed count in progress, journal
lastRun summary, end-of-run card and history line, and a Check again
button labelled with the remaining steps. versionCode 18.
Sign in to join this conversation.
No reviewers
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rhelwig/DecentSite!8
No description provided.