Publish timing: Auth history + CSV export, Admin IPFS upload timing, ETA stub (#6) #9

Closed
rhelwig wants to merge 0 commits from feat/publish-timing-logs into main
Owner

Part of #6 (publish timing logs, ETA). Branch is based on main @ d379421.

What's in it

Auth engine (c1fd3ee)

  • executeRelease records per-item timing: bytes of the reviewed properties, totalMs, and stagesMs (checking / signing / broadcasting / verifying), plus a run total. onStep carries timing on each outcome.

Auth app (3a523e4) — Auth 0.1.19 (versionCode 20)

  • New PublicationTiming (protocol module): strict parse of engine timing, CSV export, median-based ETA.
  • ReleaseJournal.timing() keeps the newest 20 runs per receipt in timingRuns; kept after publish so ETAs keep learning. Best effort: a timing save failure never changes the publication outcome.
  • Publication history: last-run headline (steps, duration, KB, median per confirmed step); per-step stage times under technical details; Export timing log (CSV) via the share sheet.
  • Fee screen: "Estimated publishing time" = median confirmed-step time of recent runs × remaining steps.

Admin (3a523e4)

  • prepareTabletReleaseRequest returns timing: phases (snapshot, platformReads, uploads, inspect) and per-blob IPFS put / read-back ms + bytes.
  • Review prep and QR handoff upload append to <dataRoot>/logs/publish-timing.jsonl (0600, trimmed to 500 lines once past 2 MB, best effort).
  • Prepare review page shows an ETA from earlier preparations (median fixed overhead + per-blob upload time).

Privacy: timing data holds record type, status, sizes and durations only. No record IDs, CIDs, contents, keys or SDK error text.

Docs: SPECS (publishing timing paragraph), IMPLEMENTATION-PLAN.

Tests

  • npm test: 169/169 pass (adds tests/publish-timing.test.ts; baseline was 167).
  • npm run typecheck: clean.
  • ./gradlew :protocol:test (JDK 21): all suites pass, including the new PublicationTimingTest (3 tests).
  • :app:assembleDebug -PauthNetwork=mainnet: builds. APK on the laptop at ~/Projects/DecentSite-auth-credits/apk/decentsite-auth-0.1.19-mainnet-debug.apk (same debug key). Not installed on any device yet.

Still open on #6

  • Per-stage ETA model and a live progress ETA during publishing.
  • Experiments: inspect once per run, parallel proof reads, concurrent IPFS uploads.
  • Needs a real publish run to collect data (no Dash spent here).
Part of #6 (publish timing logs, ETA). Branch is based on `main` @ d379421. ## What's in it **Auth engine** (c1fd3ee) - `executeRelease` records per-item `timing`: bytes of the reviewed properties, `totalMs`, and `stagesMs` (checking / signing / broadcasting / verifying), plus a run total. `onStep` carries timing on each outcome. **Auth app** (3a523e4) — Auth **0.1.19** (versionCode 20) - New `PublicationTiming` (protocol module): strict parse of engine timing, CSV export, median-based ETA. - `ReleaseJournal.timing()` keeps the newest 20 runs per receipt in `timingRuns`; kept after publish so ETAs keep learning. Best effort: a timing save failure never changes the publication outcome. - Publication history: last-run headline (steps, duration, KB, median per confirmed step); per-step stage times under technical details; **Export timing log (CSV)** via the share sheet. - Fee screen: "Estimated publishing time" = median confirmed-step time of recent runs × remaining steps. **Admin** (3a523e4) - `prepareTabletReleaseRequest` returns `timing`: phases (snapshot, platformReads, uploads, inspect) and per-blob IPFS put / read-back ms + bytes. - Review prep and QR handoff upload append to `<dataRoot>/logs/publish-timing.jsonl` (0600, trimmed to 500 lines once past 2 MB, best effort). - Prepare review page shows an ETA from earlier preparations (median fixed overhead + per-blob upload time). **Privacy:** timing data holds record type, status, sizes and durations only. No record IDs, CIDs, contents, keys or SDK error text. **Docs:** SPECS (publishing timing paragraph), IMPLEMENTATION-PLAN. ## Tests - `npm test`: 169/169 pass (adds `tests/publish-timing.test.ts`; baseline was 167). - `npm run typecheck`: clean. - `./gradlew :protocol:test` (JDK 21): all suites pass, including the new `PublicationTimingTest` (3 tests). - `:app:assembleDebug -PauthNetwork=mainnet`: builds. APK on the laptop at `~/Projects/DecentSite-auth-credits/apk/decentsite-auth-0.1.19-mainnet-debug.apk` (same debug key). **Not installed on any device yet.** ## Still open on #6 - Per-stage ETA model and a live progress ETA during publishing. - Experiments: inspect once per run, parallel proof reads, concurrent IPFS uploads. - Needs a real publish run to collect data (no Dash spent here).
- Auth protocol: PublicationTiming (strict parse, CSV export, median ETA);
  ReleaseJournal keeps newest 20 timing runs per receipt, kept after publish.
- Auth UI: Publication history shows last-run timing and per-step stage
  times; Export timing log (CSV) via share sheet; fee screen ETA.
  Auth 0.1.19 (versionCode 20).
- Admin: prepareTabletReleaseRequest returns phase and per-blob IPFS
  put/read-back timing and sizes; review prep and QR handoff append to
  <dataRoot>/logs/publish-timing.jsonl; Prepare review page shows an ETA.
- No record IDs, CIDs, contents, keys or SDK text in timing data.
- SPECS + IMPLEMENTATION-PLAN updated. npm test 169/169, :protocol:test green.
Author
Owner

Merged into main locally and pushed: merge commit 2b95a21 (main now at 5f3298b). Full test suite 169/169 passed on the branch before merge. Closing (Forgejo did not auto-detect the merge).

Merged into main locally and pushed: merge commit 2b95a21 (main now at 5f3298b). Full test suite 169/169 passed on the branch before merge. Closing (Forgejo did not auto-detect the merge).
rhelwig closed this pull request 2026-10-10 18:51:56 +00:00

Pull request closed

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!9
No description provided.