@c4roa0/agentpay-user 0.3.5 → 0.3.7

package/doc/README.md

@@ -1,5 +1,7 @@
 # User documentation
 
+- [Existing-installation update acceptance](records/npm-update-participant-2026-11-11.md): participant update to User 0.3.6 / Wallet 0.3.3 and retained records.
+
 - [Directory npm update verification](records/local-npm-update-2026-11-08.md): real package update and preflight boundary.
 
 ## Start by role

package/doc/TODO.md

@@ -1,23 +1,39 @@
 # User TODO
 
+- [x] Participant directory-local update to User 0.3.6 / Wallet 0.3.3: running versions, original Orders in CLI/Market and available result cache verified (2026-11-11).
+- [ ] Fresh-install and interrupted-update acceptance remain separate; discuss scope before execution.
+
+
+- [x] Clarify full Cache IDs and missing details argument; support bounded, unique read-only short-ID lookup (2026-11-11).
+- [ ] Publish cache-details guidance with the next reviewed User release.
+
+
+- [x] Clarify npm update preview with actual installed Wallet versus target, unchanged and unknown states (2026-11-11).
+- [ ] Include update-preview wording in the next reviewed User release; no new release was made for this edit.
+
+
+- [x] Preserve maintenance error guidance and original request identity; controlled HTTP/IPC verification (2026-11-10).
+- [x] Publish User 0.3.6 with exact Wallet 0.3.3 dependency; registry identity/integrity verified (2026-11-10).
+
 ## 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 +49,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 +68,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 +76,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 +87,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/doc/records/npm-update-participant-2026-11-11.md

@@ -0,0 +1,25 @@
+# Existing npm installation update acceptance
+
+Date: 2026-11-11. Evidence: participant terminal output and website confirmation.
+
+The participant updated a directory-local npm installation through `agentpay update`:
+User 0.3.5 to 0.3.6, with matching Wallet 0.3.3. The update repaired service paths,
+restarted Wallet and Runtime, and verified official test Skill 1.2.1 against the
+built-in SHA-256 without starting a purchase. After deliberate unlock, status
+reported Wallet 0.3.3 and Runtime 0.3.6 running, with local history checks complete.
+
+Both saved Orders remained settled. Policy validity, login startup and the locally
+saved Market connection remained present. The participant confirmed both Orders
+were still visible on the website. The retained result cache listed its original
+timestamp and Order association, and details reported the JSON result available
+(28-byte content, approximately 3.4 KiB retained storage). No export or independent
+byte-by-byte backup comparison was performed. The older Order's missing local
+result was already present before updating and was not resolved by this update.
+
+Two usability findings were corrected in source: show installed and target Wallet
+versions separately, and clarify full Cache IDs with bounded unique short-ID lookup
+for read-only details. Controlled tests passed; these fixes are not in npm 0.3.6.
+
+This accepts the observed existing-installation update and retained records. It
+is not fresh-install, interrupted-update recovery, financial reconciliation or
+real-network acceptance. No new payment or authorization was required.

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@c4roa0/agentpay-user",
-  "version": "0.3.5",
+  "version": "0.3.7",
   "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,86 @@
 # AgentPay User progress
 
+## User 0.3.7 release preparation — 2026-11-11
+
+Patch release includes installed/target Wallet version preview and clearer Cache ID
+help with unique short-ID lookup for read-only details. Wallet remains pinned to
+0.3.3 and Protocol to 0.14.3. Manifest, lockfile and update-pair versions are aligned.
+Publication and registry verification are pending; no local participant service or
+private data is changed by preparing the release.
+
+
+## Existing client update accepted — 2026-11-11
+
+Participant directory-local npm update to User 0.3.6 / Wallet 0.3.3 completed.
+Running versions, unlocked Wallet, two settled Orders, unchanged saved validity,
+startup/Market connection and retained available result cache were observed.
+Participant confirmed both original Orders remain visible on Market. The older
+missing result predates this update. No new payment or Policy was created.
+[Evidence and limits](doc/records/npm-update-participant-2026-11-11.md). Update-preview and Cache ID guidance fixes are
+verified in source, not yet published. Fresh installation and interrupted-update
+acceptance remain next for discussion; neither has started in this loop.
+
+
+## Cache details guidance — 2026-11-11
+
+Missing details IDs now show a short example before accessing local storage.
+List guidance explains that the namespace is part of the ID. Read-only details
+accept a unique prefix with at least eight hexadecimal characters; ambiguous,
+missing or incomplete bounded lookups require a full ID. Export and cleanup keep
+their existing exact-identity rules. All 19 targeted cache/CLI regressions passed
+with isolated process tests outside the restricted sandbox; no live cache changed.
+Source only, pending publication. There is no input: ID namespace: inputs use the
+attachment ID shown by list, while results can use result: or runtime-result:0x.
+
+
+## Update preview clarity — 2026-11-11
+
+The confirmation screen now lists installed User and Wallet versions separately
+from update targets. Wallet is read from the installed dependency, not inferred
+from User's requested dependency. Unchanged versions are explicit; unreadable or
+missing Wallet metadata shows “not confirmed” without blocking the normal repair
+through npm. Controlled update tests cover all three cases and cancellation without
+service/install mutation. This source change is not yet published; running-process
+versions remain the responsibility of status after update/restart.
+
+
+## User 0.3.6 published — 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. Published through matching tag v0.3.6 after 391 behavior tests and independent
+installation/lifecycle checks. Public npm metadata and SHA-512 match the verified
+archive. 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. These changes were subsequently published in 0.3.6; see the release record above.
+
+
+## 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 +90,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 +481,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/cache-management-cli.mjs

@@ -128,6 +128,11 @@ export async function runCacheManagement(
     }
   const usage =
     "Usage: agentpay cache [info | list [PAGE] [input|output] [--state STATE] [--request ID | --order ID] | details ID | export ID PATH | clean | settings [KEY VALUE]]\nAdd --offline only when managing stopped Runtime storage. Wallet unlock is not required.";
+  if(action === "details" && rest.length === 0){
+    write("Choose a Cache ID from agentpay cache list. Copy the whole ID, including any prefix such as result:.");
+    write("Example: agentpay cache details result:5aa18b50\nA unique short ID needs at least 8 hexadecimal characters.");
+    return 2;
+  }
   if (
     invalidFilter ||
     !["summary", "list", "details", "export", "clean", "settings"].includes(
@@ -192,7 +197,7 @@ export async function runCacheManagement(
           ...(rest[1] ? { purpose: rest[1] } : {}),
         });
       write(
-        `\n${r.total} entries · page ${page}\nDetails: agentpay cache details <Cache ID>`,
+        `\n${r.total} entries · page ${page}\nDetails: agentpay cache details <Cache ID>\nCopy the full ID including its prefix, or use a unique short ID (8+ hex characters).`,
       );
       if (!r.items.length)
         write("No saved results or attachments match this view.");
@@ -222,7 +227,32 @@ export async function runCacheManagement(
             .join("")}`,
         );
     } else if (action === "details") {
-      const r = await operate({ action, id: rest[0] });
+      let id=rest[0];
+      if(!/^(?:result:|runtime-result:0x)?[0-9a-f]{64}$/.test(id)){
+        if(!/^(?:result:|runtime-result:0x)?[0-9a-f]{8,63}$/.test(id)){
+          write('Use the Cache ID from agentpay cache list, or its first 8 or more hexadecimal characters.');
+          return 2;
+        }
+        // Resolve only read-only details. Bound enumeration; never guess from an
+        // incomplete list or turn a short display identifier into a cleanup key.
+        const matches=new Set();let offset=0,total;
+        do {
+          const page=await operate({action:'list',offset,limit:100});
+          if(page.total>1000 || total!==undefined&&page.total!==total || !page.items.length&&offset<page.total){
+            write('Use the full Cache ID; the cache is too large or changed during lookup.');return 2;
+          }
+          total=page.total;
+          for(const row of page.items){
+            const key=id.includes(':')?row.id:row.id.replace(/^(?:result:|runtime-result:0x)/,'');
+            if(key.startsWith(id))matches.add(row.id);
+          }
+          if(matches.size>1){write('More than one cache entry matches. Copy a longer or full Cache ID from agentpay cache list.');return 2;}
+          offset+=page.items.length;
+        }while(offset<total);
+        if(!matches.size){write('No cache entry matches. Run agentpay cache list and copy its Cache ID.');return 2;}
+        id=[...matches][0];
+      }
+      const r = await operate({ action, id });
       write(
         `${safe(r.filename)}\n  ${contentSize(r)} · ${r.state}\n  ${r.requestId ? "Request" : "Order"}: ${safe(r.requestId || r.orderId)}\n  File key: ${safe(r.fileKey)}\n  SHA-256: ${r.sha256 || "Not available"}\n  Updated: ${new Date(r.updatedAtMs).toLocaleString()}`,
       );

package/src/npm-update.mjs

@@ -7,6 +7,7 @@ import { access, appendFile, copyFile, chmod, lstat, mkdir, mkdtemp, open, readF
 import { constants } from 'node:fs';
 import { basename, dirname, isAbsolute, join, resolve } from 'node:path';
 import { randomUUID } from 'node:crypto';
+import { createRequire } from 'node:module';
 import { createInterface } from 'node:readline/promises';
 import { installedUserDir, resolveUserDataDir, rememberUserDataDir } from './local-data-directory.mjs';
 import { installationDirectory } from './installation-paths.mjs';
@@ -91,7 +92,18 @@ export async function updateFromNpm({
       await officialTest({userDir,dataDir,write});
       return 0;
     }
-    write(`User ${current.version} → ${metadata.version} · Wallet ${metadata.dependencies['@c4roa0/agentpay-wallet']}`);
+    // Read the installed dependency, not the version requested by User's manifest.
+    // Missing/broken packages must not prevent npm from repairing the installation.
+    let walletVersion;
+    try {
+      const file = createRequire(join(userDir,'package.json')).resolve('@c4roa0/agentpay-wallet/package.json');
+      const wallet = JSON.parse(await readFile(file,'utf8'));
+      if(wallet.name === '@c4roa0/agentpay-wallet' && stable(wallet.version)) walletVersion = wallet.version;
+    } catch {}
+    const targetWallet = metadata.dependencies['@c4roa0/agentpay-wallet'];
+    write('Installed packages → update target');
+    write(`User    ${current.version} → ${metadata.version}`);
+    write(`Wallet  ${walletVersion === targetWallet ? `${walletVersion} (unchanged)` : `${walletVersion || 'not confirmed'} → ${targetWallet}`}`);
     write(`Installation folder: ${target.prefix}`);
     write('Background services will pause. Keys, permissions, Orders and cache are kept.');
     if (!force && (await ask("Type 'confirm' to update, or 'q' to cancel")).trim().toLowerCase() !== 'confirm') {

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.7",
+  "walletVersion": "0.3.3",
   "typesDependency": "0.14.3"
 }