@c4roa0/agentpay-user 0.3.5 → 0.3.6

package/doc/TODO.md

@@ -1,23 +1,27 @@
 # User TODO
 
+- [x] Preserve maintenance error guidance and original request identity; controlled HTTP/IPC verification (2026-11-10).
+- [ ] Include maintenance guidance in the next reviewed npm release; no release performed by this change.
+
 ## Existing Market address update
 
 - [x] Allow source-to-npm reconnect without an onboarding draft; verify Policy contracts and preserve missing files.
-- [ ] Publish 0.3.5 and retry the participant address update.
+- [x] Publish 0.3.5 and independently verify registry integrity.
+- [x] Retry the participant address update without old onboarding files. Observed User 0.3.5 / Wallet 0.3.2 on 2026-11-09.
 
 - [x] Reauthenticate and verify original account, Wallet tuple and Policy connection before replacing an address.
 - [x] Verify unchanged deployment; preserve RPC, key, Policy, history/cache and original cancellation IDs.
 - [x] Apply under installer lock, restart managed Runtime, retain retry marker and show incomplete update in status.
 - [x] Full regression (387 checks), followed by targeted reconnect-boundary/transaction checks.
 - [x] Publish User 0.3.4 through v0.3.4; workflow and independent registry integrity verification passed.
-- [ ] Verify the existing participant installation and explicit address update against HTTPS.
+- [x] Verify the existing participant installation and explicit address update against HTTPS. Observed User 0.3.5 / Wallet 0.3.2 on 2026-11-09.
 
 ## Directory npm update, then HTTPS
 
 - [x] Support directory-local npm update without replacing source/link installs.
 - [x] Verify real npm directory upgrade and isolated preflight; nine regression checks passed.
 - [x] Publish 0.3.3 via v0.3.3 and independently verify registry archive/dependency pins.
-- [ ] Verify participant directory install/update.
+- [x] Verify participant directory install/update. Observed User 0.3.5 / Wallet 0.3.2 on 2026-11-09.
 
 ## Tag-triggered publication
 
@@ -33,14 +37,15 @@
 - [x] Verify website visibility and independently reconcile Settlement/chain outcome; prepare User 0.3.2 candidate.
 - [x] Pin the verified public Wallet 0.3.2; align package/lockfile/update-pair.
 - [x] Publish User 0.3.2 through tag-triggered OIDC; verify public registry archive.
-- [ ] Accept a real participant npm update/restart.
+- [x] Accept a real participant npm update/restart. Observed User 0.3.5 / Wallet 0.3.2 on 2026-11-09.
 
 
 ## Fixed Skill download loop — 2026-11-08
 
 - [x] Request the official ZIP by the built-in SHA-256; reject unavailable/substituted versions without fallback.
 - [x] Complete fixed-download regression/type checks and publication/deletion review; the separate Market schema-fixture issue was resolved in its later regression.
-- [ ] After Market API/Web/nginx support is live, publish the next User version (not 0.3.1 again) and verify old pinned ZIP download and participant upgrade.
+- [x] Publish later User versions and accept participant update through 0.3.5.
+- [ ] Independently verify retained old pinned ZIP download; current package acceptance alone does not close historical-version availability.
 
 
 ## Running-version release loop — 2026-11-07
@@ -51,7 +56,7 @@
 - [x] Wallet 0.3.1 published through the configured workflow; public npm version/dependencies verified.
 - [x] Pin User 0.3.1 to published Wallet 0.3.1; pairing metadata/lockfile and standalone archive verification complete.
 - [x] Publish User 0.3.1; verify public npm/latest and successful Wallet/User OIDC runs.
-- [ ] Verify real published-version update/restart on the participant installation.
+- [x] Verify real published-version update/restart on the participant installation. Observed User 0.3.5 / Wallet 0.3.2 on 2026-11-09.
 
 
 ## npm update follow-up — 2026-11-07
@@ -59,7 +64,7 @@
 - [x] Implement confirmed `agentpay update [-f]`, exact User target and matching Wallet; invoke new repair and pinned official Skill check.
 - [x] Fix relocation preparation ordering, matching legacy purge and packaged document links.
 - [x] Complete update/migration regressions (374 full-suite and 35 final targeted checks) and real npm replacement of local candidate artifacts; controlled service/registry dependencies.
-- [ ] After User release, verify a real published-version npm upgrade and participant service recovery.
+- [x] Verify published-version directory npm update and participant service recovery: User 0.3.5 / Wallet 0.3.2, 2026-11-09. Deliberate interruption remains separate.
 
 ## npm client distribution — 2026-11-07
 
@@ -70,7 +75,8 @@
 - [x] Step 3: migrate User to Wallet npm dependency and `agentpay` entry; remove sibling/build assumptions; isolated tarball/process acceptance passed.
 - [x] Step 4a: exact installed-package checks, service-path/client relocation, installer lock, recovery-safe preparation and explicit uninstall modes.
 - [x] Step 4b implementation: installed/running version and interface checks.
-- [ ] Step 4b acceptance: participant upgrade/interruption recovery (same gate as the running-version loop above).
+- [x] Step 4b participant existing-installation update/restart and HTTPS original-Order read recovery (2026-11-09).
+- [ ] Step 4b deliberate interrupted-upgrade acceptance; normal restart recovery does not close this case.
 - [ ] Step 5: publish Wallet then User via OIDC; verify registry installs and update Market guides.
   - [x] Wallet 0.3.0 first Token publication; registry integrity/latest and fresh public install/CLI/IPC verified.
   - [x] Owner configured Wallet npm Trusted Publisher; validated by 0.3.1 publication.

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@c4roa0/agentpay-user",
-  "version": "0.3.5",
+  "version": "0.3.6",
   "type": "module",
   "dependencies": {
     "@c4roa0/agentpay-protocol": "0.14.3",
-    "@c4roa0/agentpay-wallet": "0.3.2",
+    "@c4roa0/agentpay-wallet": "0.3.3",
     "ethers": "^6.17.0",
     "fs-native-extensions": "1.5.3"
   },

package/progress.md

@@ -1,5 +1,43 @@
 # AgentPay User progress
 
+## User 0.3.6 release candidate — 2026-11-10
+
+Pins published Wallet 0.3.3, retaining Protocol 0.14.3. Maintenance errors provide
+same-request guidance without automatic write retries. Package manifest, lockfile
+and update-pair metadata agree. Publication uses the matching v0.3.6 tag after
+independent installation and behavior checks; completion is not implied by this
+candidate record. No local data, Policy or service changes occur on publication.
+
+
+## Maintenance guidance — 2026-11-10
+
+Added explicit maintenance guidance without automatic write retries or replacement
+purchases. Controlled HTTP/IPC tests verify that retry retains original request
+identifiers. This is source verification, not live financial acceptance. Changes
+have not been published to npm.
+
+
+## Acceptance bookkeeping — 2026-11-10
+
+Existing-installation npm update/restart and HTTPS original-Order read recovery
+are closed by the 2026-11-09 participant evidence below. Older pending publication
+and migration paragraphs are historical checkpoints, not instructions to repeat
+the accepted update. Deliberate upgrade interruption, clean installation/uninstall
+and historical pinned-download availability remain separate acceptance items.
+No runtime code or package version changed in this documentation closeout.
+
+
+## Participant HTTPS address update accepted — 2026-11-09
+
+Participant directory-npm installation reports User 0.3.5 / Wallet 0.3.2.
+Market reconnect completed with the existing Wallet and Policy. With Anvil 8547
+forwarded, explicit Settlement Order read succeeded over HTTPS; subsequent Runtime
+status recovered to 2 saved / 2 settled / 0 waiting. The one older missing result
+predates this update and is retained. Initial unavailable checks cleared on retry.
+No new paid Order, Policy replacement or result recovery was performed. This closes
+the observed existing-installation update/address/read-recovery loop, not fresh
+installation, a new HTTPS paid journey or real-network acceptance.
+
 ## Missing onboarding draft during npm address update — 2026-11-09
 
 Participant 0.3.4 reconnect stopped before address writes because an old onboarding
@@ -9,7 +47,8 @@ present. No RPC, Policy, test configuration or private history is synthesized.
 389 full regressions passed, followed by targeted error-guidance checks. Missing
 drafts still reject contract drift; preflight errors explain the stage, preserved
 state and retry action, while interrupted writes warn about partial updates.
-User 0.3.5 publication is pending;
+User 0.3.5 published from tag v0.3.5 (6c57c12). GitHub run 42575980847
+and independent registry archive verification passed;
 participant migration remains unverified.
 
 ## User 0.3.4 published — 2026-11-09
@@ -399,9 +438,11 @@ approval. Detailed operational records are not distributed in this repository.
 
 ## Next work
 
-Public source preparation is complete within the recorded review scope. Next is the approved
-[distribution plan](doc/plans/user-wallet-distribution.md): a supported public Wallet
-client/version boundary and combined release archive. No automatic source updater.
+Public npm distribution and the existing-participant update/HTTPS loop are verified
+within the recorded scope. User pins Wallet and Protocol packages; npm update is
+available. Combined release archives remain optional, not the next installation
+prerequisite. Remaining compatibility and fresh-install checks follow the
+[distribution plan](doc/plans/user-wallet-distribution.md).
 
 Official test network mapping, deployment/artifact handoff, complete interrupted owner
 signing and real-network acceptance remain open. macOS and graphical unlock remain

package/src/runtime-client.mjs

@@ -676,7 +676,7 @@ async function invokeSaved(
       WALLET_LOCKED:
         "From the User repository, run agentpay wallet unlock, then resume this request.",
       SERVICE_MAINTENANCE:
-        "Service is under maintenance. Resume this request later.",
+        "The service is under maintenance. Try this same request later; do not create a replacement purchase.",
       SERVICE_NOT_READY:
         "Service is not ready. Check its status, then resume this request.",
     };

package/update-pair.json

@@ -1,6 +1,6 @@
 {
   "format": "agentpay.local-update-pair.v1",
-  "userVersion": "0.3.5",
-  "walletVersion": "0.3.2",
+  "userVersion": "0.3.6",
+  "walletVersion": "0.3.3",
   "typesDependency": "0.14.3"
 }