@c4roa0/agentpay-user 0.3.0 → 0.3.2

package/AGENTS.md

@@ -135,3 +135,13 @@ load Protocol fixtures from the pinned public package, not a source checkout.
 Do not remove scripts merely because their name contains smoke or Anvil: some are
 current onboarding entries. Review callers first. Never weaken signer or payment
 boundaries to simplify tests. Keep source maps and behavioral evidence limits current.
+
+## Tag-triggered npm releases
+
+Package version `X.Y.Z` is released by pushing tag `vX.Y.Z` at the exact reviewed
+source commit. `.github/workflows/publish.yml` validates this match, verifies the
+package, publishes through OIDC and checks registry integrity. Pushing a release
+tag is a publication action and needs maintainer authorization; ordinary branch
+pushes do not publish. Never move an existing release tag. Verify registry state
+before rerunning a failed publication. The `npm-publish` environment must allow
+release tags (for example `v*`), not only the main branch.

package/README.md

@@ -8,13 +8,14 @@ User is the Agent/Skill runtime, not a Provider server or a general-purpose wall
 It retains request identity and local results so interruptions can be recovered
 without silently creating a replacement purchase.
 
-## Install
+## Install with npm
 
-Use Linux with Node.js 22.22.3 or newer and npm. Install User; its reviewed Wallet
-and Protocol dependencies are included automatically:
+On Linux, prepare Node.js 22.22.3 or newer, npm and your AgentPay Market address.
+Install User with the command below. It automatically installs the matching Wallet
+and Protocol packages; you do not need to download two repositories:
 
 ```sh
-npm install --global @c4roa0/agentpay-user@0.3.0
+npm install --global @c4roa0/agentpay-user
 agentpay install --market https://YOUR_MARKET_ORIGIN
 ```
 
@@ -22,19 +23,6 @@ Replace the Market URL with your platform's address. Use a user-owned Node/npm
 installation with Node and npm's executable directory on PATH. No Wallet checkout,
 Corepack, pnpm or TypeScript build is needed.
 
-For contributors or source ZIP users:
-
-```sh
-git clone https://github.com/c4rO-0/agentpay-user.git user
-cd user
-npm ci
-npm link
-agentpay help
-```
-
-`npm link` exposes the command from your checkout. Without linking, `./run` (or
-`sh run`) provides the same commands; `AGENTPAY_NODE` can select your Node executable.
-
 Install verifies dependencies, downloads public settings and continues setup.
 You choose the Safe and spending limits, then approve with its owner wallet.
 The optional official payment test asks before spending. Never enter an owner
@@ -63,6 +51,19 @@ update their files, run `npm ci`, then `agentpay repair`. [Commands](doc/runbook
 
 ## Develop or integrate
 
+For contributors or source ZIP users:
+
+```sh
+git clone https://github.com/c4rO-0/agentpay-user.git user
+cd user
+npm ci
+npm link
+agentpay help
+```
+
+`npm link` exposes the command from your checkout. Without linking, `./run` (or
+`sh run`) provides the same commands; `AGENTPAY_NODE` can select your Node executable.
+
 - [Developer guide](doc/develope.md): independent checkout, focused tests and evidence limits.
 - [Architecture](doc/architecture.md): source map and recovery/authorization boundaries.
 - [Skill author guide](doc/runbooks/runtime-skill-client.md): call the shared Runtime client.

package/doc/TODO.md

@@ -1,5 +1,39 @@
 # User TODO
 
+## Tag-triggered publication
+
+- [x] Use matching `vX.Y.Z` tags for npm publication; retain verification gates.
+- [x] Owner confirmed release tags allowed in the GitHub `npm-publish` environment.
+- [ ] Verify the first tag-triggered OIDC publication and registry integrity.
+
+## Official package 1.2.1 — 2026-11-08
+
+- [x] Review actual published bytes, update the built-in official pin and verify fixed-download checks. Real Market fixed-version download/install repeated successfully in an isolated directory.
+- [x] Inspect this participant installation’s prior-version official tests: saved 1.2.0 record is acknowledged; retained unchanged. This does not assert every user has completed old tests.
+- [x] Load the reviewed User source update and run the normal 1.2.1 payment test with explicit user consent; terminal delivery/result/ack completed.
+- [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.
+- [ ] Publish User 0.3.2 through OIDC and verify registry artifact; then accept a real npm update.
+
+
+## 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.
+
+
+## Running-version release loop — 2026-11-07
+
+- [x] Verify User 0.3.0 public-registry publication; Trusted Publisher configured.
+- [x] Verify actual installed Protocol versions from both consumer resolution paths.
+- [x] Add process-start software reporting and status/repair mismatch handling; isolated checks passed.
+- [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.
+
+
 ## npm update follow-up — 2026-11-07
 
 - [x] Implement confirmed `agentpay update [-f]`, exact User target and matching Wallet; invoke new repair and pinned official Skill check.
@@ -15,11 +49,12 @@
 - [x] Review step 2: guard normal packing against missing/stale builds, correct public-interface docs and verify a standalone TypeScript consumer.
 - [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.
-- [ ] Step 4b: running-daemon version/interface negotiation and participant upgrade/interruption acceptance.
+- [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).
 - [ ] 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 (pending validation).
-  - [ ] Validate Wallet OIDC with a later reviewed release. User publication and Market guide updates remain pending.
+  - [x] Owner configured Wallet npm Trusted Publisher; validated by 0.3.1 publication.
+  - [x] Wallet and User OIDC validated by 0.3.1 releases; Market guide updates remain pending.
 - [ ] Step 6: participant setup/upgrade/restart/uninstall and official Anvil paid acceptance.
 
 
@@ -48,7 +83,7 @@
 ## Independent distribution (next development loop)
 
 - [ ] Define the supported Wallet client/IPC boundary and source/build/running compatibility requirements.
-- [ ] Replace exact version pairing with reviewed compatibility checks; preserve keys, Policies and recovery.
+- [ ] Optional later: widen exact reviewed dependency pairs only with a verified compatibility matrix; preserve keys, Policies and recovery.
 - [ ] Optional later: combined ZIP/platform assets after primary npm installation acceptance.
 - [ ] Verify fresh Git/ZIP installation and missing/incompatible/stale version recovery; update Market guidance.
 

package/doc/architecture.md

@@ -18,7 +18,7 @@ logic or platform storage. No Settlement checkout or database access is required
 ## Shared Protocol dependency
 
 User and Wallet pin `@c4roa0/agentpay-protocol@0.14.3` from npm. Their lockfiles
-record integrity. The current repair gate still checks the exact repository versions
+record integrity. The current repair gate still checks the exact package versions
 and shared Protocol dependency in `update-pair.json`; `typesDependency` is the
 retained v1 field name for that npm version. It is not a compatibility range.
 Installation/repair fingerprints cover manifests and lockfiles rather than a vendor
@@ -85,8 +85,11 @@ verification before binding. A lost response resumes the original plan.
 ## External dependencies and development boundary
 
 User resolves the installed Wallet package through public client, local-administration
-and CLI exports. Exact reviewed dependency versions are checked; independent
-running-process compatibility negotiation remains planned. User imports ethers from its own
+and CLI exports. `wallet-package.mjs` verifies the exact reviewed pair;
+`protocol-package.mjs` resolves each consumer's actual Protocol installation, including
+nested npm dependencies. `software-versions.mjs` compares process-start reports with
+the installed pair during status/repair. User 0.3.1 pins Wallet 0.3.1 for these checks; broader compatibility ranges remain deferred.
+User imports ethers from its own
 declared dependency. The pinned public Protocol package provides types, hashes and
 fixtures. No Agent, Protocol source checkout or private platform repository is
 required for the local test suite.

package/doc/plans/user-wallet-distribution.md

@@ -9,8 +9,8 @@ Repositories, processes and releases remain separate; Node is still required.
 Ordinary users install `@c4roa0/agentpay-user` and run `agentpay setup`. User installs
 its reviewed Wallet dependency; both consume public Protocol. No sibling source
 folders, pnpm or local TypeScript build are required for the published User path.
-Wallet remains independently installable. Git checkouts are for contributors; the User 0.3.0 candidate now uses the same
-public Wallet package. User npm publication remains a separate release step.
+Wallet remains independently installable. Git checkouts are for contributors; the User 0.3.0 release uses the public Wallet package. User 0.3.1 pairs with
+Wallet 0.3.1 for running-version verification; publication remains a separate release step.
 Combined ZIPs and platform binaries are optional later work, not a release prerequisite.
 
 npm installation only installs program files. Key creation, background-service

package/doc/reference/npm-integration-verification.md

@@ -65,3 +65,39 @@ The existing official-package tests cover pinned digest rejection and preservati
 The updater follows npm's [install](https://docs.npmjs.com/cli/v11/commands/npm-install/)
 and [view](https://docs.npmjs.com/cli/v11/commands/npm-view/) command interfaces.
 A released-version registry upgrade and participant recovery still need acceptance.
+
+## Running-process reporting follow-up — 2026-11-07
+
+User 0.3.0 first publication was verified against the public registry. User and Wallet
+Trusted Publishers are configured; first OIDC validation is still pending.
+
+The next candidate checks process-start package/interface/Protocol metadata during
+status and repair. User regressions: 378 passed; Wallet behavioral suite: 30 passed.
+Wallet tarball consumption passed real CLI/IPC checks. A disposable User install with
+a local Wallet 0.3.1 archive and temporary test-only dependency pin passed real process
+startup/restart and key preservation. Missing/mismatched reports prevent repair from
+recording success. No Policy, Order or participant service was changed.
+
+These results do not establish a published-version upgrade: publish Wallet 0.3.1,
+then update User's exact pin, lockfile and pairing metadata and verify its final archive.
+The repository still pins public Wallet 0.3.0 until that release exists.
+
+## Actual installed Protocol verification — 2026-11-08
+
+Preflight checks resolved package versions from both User and Wallet, including a
+nested Wallet dependency. A mismatched copy is rejected even if both consumer
+manifests declare the expected version. Process reporting records the resolved
+version at startup. Wallet's 30 tests and standalone archive CLI/IPC checks passed;
+User's final 378-test suite passed after updating a dependency-less test fixture.
+This is local compatibility verification, not a guarantee against altered package files.
+Wallet candidate `7e4d4fa` is pushed; OIDC publication and User exact pin/lockfile
+update remain the release gate.
+
+## User 0.3.1 final pairing — 2026-11-08
+
+User 0.3.1 pins public Wallet 0.3.1 and Protocol 0.14.3. Lockfile integrity came from
+the public registry; no local file dependency or sibling checkout is required.
+The complete suite passed (378 tests). The npm archive installed independently,
+exposed `agentpay`, and started/restarted real disposable Wallet/Runtime processes
+with matching software reports while preserving the key and starting Wallet locked.
+Publication via GitHub OIDC and participant upgrade remain separate pending steps.

package/doc/runbooks/commands.md

@@ -87,3 +87,17 @@ independently query the chain. If querying fails, the command labels the last
 local record and its saved check time. A successful query does not rewrite local
 history; Runtime maintains its own recovery observations. Use
 `agentpay orders details ID` for the saved local record.
+
+## Running-version checks (User 0.3.1)
+
+`agentpay status` compares the installed User/Wallet pair with the versions reported
+by the running processes. A mismatch leads to `agentpay repair`; missing reporting
+requires a paired package update first. Repair only records success after both
+processes report the expected package, local reporting interface and Protocol versions.
+These checks do not change Policy validity, Order identity or payment permissions.
+User 0.3.1 installs the required Wallet 0.3.1 dependency automatically.
+
+Protocol reporting reads the installed package resolved by that process, rather than
+copying its dependency declaration. User preflight checks both User's and Wallet's
+resolved copies against the reviewed exact version, including nested dependencies.
+Package version checks establish compatibility metadata, not file-integrity attestation.

package/doc/runbooks/npm-publication.md

@@ -1,56 +1,62 @@
 # Publish User to npm
 
-This publishes the User CLI and Runtime, with its exact reviewed Wallet dependency.
-It does not deploy platform services or alter participant keys, Policies or Orders.
+Push a reviewed `vX.Y.Z` tag to publish `@c4roa0/agentpay-user` through GitHub
+Actions. The tag must match `package.json`. Ordinary branch pushes do not publish.
+Keep `update-pair.json`, the lockfile and the reviewed Wallet dependency aligned.
+Publish the required Wallet version before releasing User.
 
-## Verify a release
+## One-time setup
 
-From a clean reviewed source checkout, using Node 22.22.3 or newer:
+In GitHub **Settings → Environments → npm-publish**, allow deployment from tags
+matching `v*`. A rule allowing only the `main` branch will block tag releases.
+Keep required reviewer approval if desired. Restrict creation, update and deletion
+of release tags to maintainers through repository rules.
 
-```sh
-npm ci --ignore-scripts
-npm test
-node scripts/test-package.mjs artifacts/npm
-```
+On npm, configure this package's Trusted Publisher:
+
+| Field | Value |
+| --- | --- |
+| Publisher | GitHub Actions |
+| Organization/user | `c4rO-0` |
+| Repository | `agentpay-user` |
+| Workflow filename | `publish.yml` |
+| Environment name | `npm-publish` |
+| Allowed action | Direct publishing |
 
-Review the package inventory and README. The archive check installs the package in
-an isolated directory, checks the public command and starts disposable Wallet/Runtime
-processes. It never uses a participant's private data. Keep the exact verified archive
-for publication; do not rebuild it between verification and upload.
+Existing matching npm trust settings need no change. The first successful OIDC
+publication validates a pending connection; a local token upload does not.
+No stored npm token is needed by this workflow.
 
-## First publication
+## Release a version
 
-Authenticate as the package maintainer, then publish the verified archive:
+1. Update `package.json` and the changelog. Review code, documentation, dependencies
+   and package contents; complete the repository's verification steps.
+2. Commit and push the reviewed source to main, including the tag-triggered workflow.
+3. Create an annotated tag at that exact commit and push it. Replace `X.Y.Z` and
+   `REVIEWED_COMMIT` below with the release version and reviewed commit:
 
 ```sh
-npm publish artifacts/npm/c4roa0-agentpay-user-0.3.0.tgz --access public --ignore-scripts --registry=https://registry.npmjs.org/
-node scripts/verify-npm-release.mjs artifacts/npm/c4roa0-agentpay-user-0.3.0.tgz 0.3.0
+git tag -a vX.Y.Z REVIEWED_COMMIT -m "Release X.Y.Z"
+git push origin vX.Y.Z
 ```
 
-Never commit or share a publishing Token. If npm stages the first release, approve
-it on npm before verifying. A timeout is not proof of failure: check the registry
-before retrying publication. Published version numbers cannot be reused.
-
-## GitHub Trusted Publisher
+Pushing the tag starts **Publish User to npm** automatically. There is no version
+input or separate Run workflow step. If the environment requires approval, approve
+that deployment in GitHub. The workflow checks the tag against the manifest before
+building, runs the existing verification gates, tests/packs the archive, publishes
+with OIDC and checks public registry integrity. It builds the tagged source, even
+if main advances. No production service or participant Wallet is upgraded.
 
-Create the GitHub environment `npm-publish` and restrict its deployment branch to
-`main`. Add maintainer approval if desired. In the npm package's Trusted Publisher
-settings, select GitHub Actions and enter:
+## Verify or recover a publication
 
-| Field | Value |
-| --- | --- |
-| Organization/user | `c4rO-0` |
-| Repository | `agentpay-user` |
-| Workflow filename | `publish.yml` |
-| Environment name | `npm-publish` |
-| Allowed action | Direct publishing |
+Check the run's **Verify public registry integrity** result and the package version
+on npm. Record the tag, source commit and result in progress. Do not claim success
+from tag creation alone. Actual OIDC validation requires the GitHub run.
 
-Run **Publish User to npm** on `main` with a new reviewed package version matching
-`package.json` and `update-pair.json`. It tests, packs, verifies, publishes that exact
-archive through OIDC, and compares registry integrity. No stored npm Token is needed.
-The first successful OIDC release validates the connection; the initial Token upload
-does not. Afterwards, disable bypass-2FA tokens and retire unused publishing tokens.
-See [npm Trusted Publishing](https://docs.npmjs.com/trusted-publishers/).
+If a run fails before upload, investigate before rerunning. If source needs a fix,
+use a new version/tag; never move an existing release tag. If upload may have
+succeeded, check registry state and archive integrity before rerunning; npm versions
+are immutable and an already-published version must not be uploaded again.
 
-Publication is not real-network or participant upgrade acceptance. Record the exact
-source revision and verification outcome; test the published installation separately.
+Publication is not participant upgrade acceptance, cross-platform verification or
+real-funds approval.

package/doc/runbooks/official-test-package.md

@@ -9,9 +9,24 @@ hash reported by the same server that supplies the ZIP.
 
 This pin applies only to the maintained onboarding test. Generic Runtime calls and
 ordinary Skill installation do not require the random service or this package.
-The current pin is the reviewed random Skill 1.2.0 private rehearsal package;
+The current pin is the reviewed random Skill 1.2.1 private rehearsal package;
 it includes its service reference. It is not a production-network release.
 
+## Download a fixed Market version
+
+Setup and repair derive `/skills/bundles/:serviceId/versions/:sha256/metadata`
+from the saved Market source, using User's built-in ZIP hash. They download the matching
+fixed ZIP on the same origin and retain any `/market` ingress prefix. They no longer
+require Market's current release to match the User release. The ZIP is still hashed
+before parsing or saving; metadata cannot override the pin.
+
+Market must retain the approved historical version and permit its public download.
+If it is absent, withdrawn or no longer approved under current checks, preparation
+stops with an unavailable message. No current-version or Provider-hosted fallback is
+used. Existing local packages, requests and spending permission are unchanged.
+This client change requires the Market fixed-version API rollout before distributing
+the next User release; User 0.3.1 and earlier do not use this endpoint.
+
 ## Before publishing a User update
 
 1. Check whether the maintained official Skill has a new published version.

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@c4roa0/agentpay-user",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "type": "module",
   "dependencies": {
-    "ethers": "^6.17.0",
-    "fs-native-extensions": "1.5.3",
     "@c4roa0/agentpay-protocol": "0.14.3",
-    "@c4roa0/agentpay-wallet": "0.3.0"
+    "@c4roa0/agentpay-wallet": "0.3.2",
+    "ethers": "^6.17.0",
+    "fs-native-extensions": "1.5.3"
   },
   "scripts": {
     "start": "node src/index.mjs",

package/progress.md

@@ -1,12 +1,156 @@
 # AgentPay User progress
 
-## User 0.3.0 first publication prepared — 2026-11-07
-
-Owner authorized the first npm publication. The package's private gate is removed;
-README now describes the npm entry and exact Wallet dependency. GitHub `publish.yml`
-uses the `npm-publish` environment and OIDC for subsequent releases. Initial Token
-upload, public-registry verification and Trusted Publisher validation are pending.
-No published-success claim is made by the prepared package or workflow.
+## User 0.3.2 release pairing — 2026-11-08
+
+Candidate now pins the verified public Wallet 0.3.2 with Protocol 0.14.3; package,
+lockfile and update-pair metadata agree. This release includes fixed-version
+Market downloads and the reviewed official Skill 1.2.1 pin. Historical notes
+below describe earlier candidate pairings. Publish through tag `v0.3.2` after
+final suite and standalone archive checks; no automatic new purchase is authorized.
+
+## Tag-triggered publication — 2026-11-08
+
+Wallet, Protocol and User release workflows now run on pushed `vX.Y.Z` tags.
+Each validates its package version, runs existing verification, publishes with
+OIDC and checks registry integrity. Branch pushes do not publish. No tag was
+pushed or npm version published for this workflow change. Owner confirmed `v*` tags allowed in the GitHub
+`npm-publish` environment; npm trust fields remain unchanged. YAML/shell checks and six executable tag/version guard cases passed
+per repository (matching version, mismatch, branch, prerelease, leading zero and
+newline rejection). Actual GitHub/OIDC execution remains pending.
+
+## Official 1.2.1 payment reconciled / User 0.3.2 candidate — 2026-11-08
+
+Participant confirmed Market Order visibility. Independent fixed-block chain reads,
+receipts and token transfers match Settlement's finalized release record: paid
+0.7 rUSDC, seller 0.665, platform fee 0.035, no refund, empty Vault. Funding,
+delivery and release events occur once for the verified Order. No further payment.
+This is private Anvil acceptance, not real-network or production approval.
+User 0.3.2 candidate includes fixed-version downloads and the reviewed official
+1.2.1 ZIP pin. Its preliminary package check used Wallet 0.3.1 and Protocol 0.14.3.
+The maintainer requested Wallet 0.3.2 review/publication first; after registry
+verification, update User’s exact dependency and reverify the final package.
+Candidate publication and real npm update acceptance remain pending.
+
+## Official Skill 1.2.1 participant payment passed — 2026-11-08
+
+Operator ran normal wallet unlock and payment-test commands after source repair.
+The guide quoted a maximum 0.7 rUSDC and 10-minute service limit; the operator
+explicitly confirmed. It reported delivery verification, saved-result verification
+and receipt acknowledgement, then completed successfully. This is private Anvil
+end-to-end participant evidence. The quoted maximum is not independently reconciled
+actual charge; payout/refund terminal chain evidence has not been checked here.
+User remains the 0.3.1-labelled source candidate, not a new published npm release.
+Next: website Order visibility and read-only Settlement/chain reconciliation before
+release closeout. Do not rerun a completed payment test just to inspect the result.
+
+## Participant repair completed — 2026-11-08
+
+Operator ran the normal source repair entry. Official Skill 1.2.1 passed the
+built-in hash check and was installed. Wallet and Runtime restarted; Wallet is
+locked as expected. Saved Policy and Market connection remain present, and local
+history reports two settled Orders plus one archived record. No purchase occurred.
+This is source-candidate repair acceptance, not publication of a new npm version.
+Next operator step unlocks Wallet and invokes the normal payment test; explicit
+current-price confirmation remains required before creating a paid Order.
+
+## Official fixed-download acceptance — 2026-11-08
+
+The normal prepareOfficialTestUpdate entry downloaded 1.2.1 twice from the running
+Market fixed-version API into an isolated directory, verified the built-in hash,
+installed successfully and preserved an existing prior-record fixture byte-for-byte.
+The first diagnostic read assumed a flat archive; it was corrected to read the saved
+publisher ZIP through User's parser. No product installation defect was found.
+17 targeted pin/download/update/payment-orchestration/prefix checks passed.
+This proves download/install behavior, not paid invocation. No participant services
+or Wallet data changed. Source repair and explicit payment acceptance are next;
+the candidate is not yet a new npm release.
+
+## Official test pin 1.2.1 prepared — 2026-11-08
+
+Reviewed the actual Provider ZIP and confirmed it matches the published fixed Market
+download: 4373 bytes, SHA-256
+`20633b314c66166f94dc6e7d7eb5bce54ab5901fb1ed314a04ea3fd49ca8a9a4`.
+The official-test pin now selects 1.2.1; generic Runtime routing is unchanged.
+The package checker and 14 controlled pin/download/update/payment-orchestration
+checks passed. The payment fixture now follows the selected version instead of
+hardcoding 1.2.0. No real payment, service restart or npm release was performed.
+Before participant testing, check for unfinished tests from the previous version:
+records are retained, but the payment-test entry selects a version-specific record.
+Do not treat a new-version test as recovery of an old purchase.
+
+
+## Development dependency verification — 2026-11-08
+
+Reinstalled dependencies from the unchanged lockfile after a stale local installation
+could not resolve the already-declared Protocol package. Fixed-download/update/prefix
+checks pass 8/8; the cross-repository publication/download/User preview regression
+passes 27/27. No dependency pins, services or user data changed. This is controlled
+verification, not a new npm release or live payment acceptance.
+
+
+## Fixed historical Skill downloads — 2026-11-08
+
+Development adds SHA-256-fixed Market metadata/ZIP routes over retained releases,
+a derived per-listing lookup, website forwarding and User official-test pin selection.
+Current publication replacement no longer changes the requested ZIP. Hidden/deleted
+listings, takedown, stale approval and damaged files remain unavailable. Historical
+internal-version ZIP routes now also respect listing visibility. No DB migration,
+Provider download dependency, service restart or payment was performed.
+Deploy Market API/Web and the nginx route allowlist first, then release the updated User; current published User
+0.3.1 does not use the new fixed-version endpoint. Verification: User 33 targeted checks, Web 7 proxy checks, Deploy 8 route/build checks
+and both Market/Web typechecks passed. Market publication regression: 69/70 passed;
+the remaining pre-existing schema fixture fails with WALLET_MAPPING_SCHEMA_INVALID.
+Controlled scanner/DB fixtures and local HTTP were used; no live database, nginx
+rollout or participant acceptance is claimed.
+
+## User 0.3.1 paired release published — 2026-11-08
+
+Public npm now contains Wallet 0.3.1 with Protocol 0.14.3. User 0.3.1 pins that
+published Wallet exactly; pairing metadata and lockfile are updated together.
+This release adds actual installed Protocol verification and running-version checks
+for status/repair. Prior release-gate notes below describe earlier checkpoints.
+User 0.3.1 passed 378 behavioral tests and standalone npm archive installation,
+including real Wallet/Runtime restart and matching running-version reports.
+User 0.3.1 is public and npm `latest`, with Wallet 0.3.1 and Protocol 0.14.3.
+[User OIDC publication](https://github.com/c4rO-0/agentpay-user/actions/runs/42440841342)
+passed from `46796ea`; [Wallet OIDC publication](https://github.com/c4rO-0/agentpay-wallet/actions/runs/42440112081)
+passed from `7e4d4fa`. Registry metadata was independently checked.
+Real published-version upgrade/restart acceptance remains pending.
+No participant services, keys, Policies or Orders are changed by package verification.
+
+## Historical checkpoints — superseded by the current release status above
+
+The dated entries below preserve evidence and earlier decisions. Their pending
+release labels are historical; use current TODO for remaining work.
+
+### Installed dependency verification / paired release — 2026-11-08
+
+User now checks the actual Protocol package resolved from User and Wallet separately,
+including nested npm copies. Process reports use resolved installed versions, not
+just dependency declarations. Wallet 0.3.1 candidate passed behavioral and independent
+package checks and is pushed as `7e4d4fa`; its OIDC publication is the next operator step.
+User remains pinned to public Wallet 0.3.0 until the new registry release exists;
+then update its exact dependency, lockfile and pairing metadata together. User changes
+remain unreleased. No participant service, key, Policy or Order was changed.
+
+## User 0.3.0 published; running-version checks in development — 2026-11-07
+
+`@c4roa0/agentpay-user@0.3.0` was published from User `86ee8e7`.
+Public registry version/latest and archive integrity matched the verified artifact.
+User and Wallet Trusted Publishers are configured; first OIDC releases remain pending.
+Earlier candidate sections below are historical, not current publication status.
+
+Wallet 0.3.1 candidate reports process-start software metadata. User status and repair
+compare running package/interface/Protocol versions against the installed pair.
+Missing reporting is unknown, never proof of compatibility. Policy format/version,
+identity and transaction authority are unchanged. Wallet behavioral tests (30) and installed-package IPC checks passed. User full
+regressions (378) passed, followed by final status checks and an isolated candidate
+Wallet/User process restart test. The candidate pair used a temporary test-only pin.
+
+Release gate: publish verified Wallet 0.3.1 first, then update User's exact Wallet pin,
+lockfile and pairing metadata and verify the combined package before publishing User.
+Current User still pins published Wallet 0.3.0; these development changes are not yet
+an installable verified release pair. No participant services/data were changed.
 
 
 ## npm update and migration review fixes — 2026-11-07

package/scripts/install-skill-bundle.mjs

@@ -7,7 +7,7 @@ import {
   verifyOfficialTestBytes,
   verifyOfficialTestDigest,
 } from "../src/official-test-package.mjs";
-import { marketDownloadUrl } from "../src/market-download-url.mjs";
+import { marketDownloadUrl, marketVersionMetadataUrl } from "../src/market-download-url.mjs";
 import { resolve } from "node:path";
 import {
   inspectInstalledBundle,
@@ -42,7 +42,7 @@ if (
 }
 if (mode === "--prepare-official-test" && !marketMode)
   throw Error("OFFICIAL_TEST_MARKET_REQUIRED");
-const url = new URL(source);
+const url = official ? marketVersionMetadataUrl(source, digest) : new URL(source);
 if (
   url.username ||
   url.password ||
@@ -62,6 +62,8 @@ if (marketMode) {
     redirect: "error",
     signal: AbortSignal.timeout(5000),
   });
+  if (official && [404, 410].includes(r.status))
+    throw Error("This official test version is unavailable in Market. Check for a reviewed User update or contact support; no replacement was selected.");
   if (!r.ok) throw new Error(`MARKET_BUNDLE_METADATA_HTTP_${r.status}`);
   const body = await r.json();
   metadata = body.result;
@@ -78,7 +80,7 @@ if (marketMode) {
     !metadata.publisherId ||
     typeof metadata.marketServiceId !== "string" ||
     metadata.marketDownloadPath !==
-      `/skills/bundles/${encodeURIComponent(metadata.marketServiceId)}/download`
+      marketDownloadUrl(url, metadata.marketServiceId).pathname.replace(/^\/market(?=\/skills\/)/, "")
   )
     throw new Error("MARKET_BUNDLE_METADATA_INVALID");
   downloadUrl = marketDownloadUrl(url, metadata.marketServiceId);

package/src/index.mjs

@@ -1,3 +1,4 @@
+import { runtimeSoftware } from "./software-versions.mjs";
 // Authenticated local invocation engine. Preserve durable request/payment checkpoints before
 // network calls; startup reconciliation observes history without creating replacement purchases.
 // SPDX-License-Identifier: MPL-2.0
@@ -127,6 +128,7 @@ const server = createServer(async (req, res) => {
       ok: true,
       result: {
         role: "user-runtime",
+        software: runtimeSoftware,
         capabilities: ["agentpay.runtime-call.v1"],
         walletTransport: "unix",
       },
@@ -144,7 +146,7 @@ const server = createServer(async (req, res) => {
     void recovery.refresh();
     return json(res, 200, {
       ok: true,
-      result: { role: "user-runtime", ...recovery.status() },
+      result: { role: "user-runtime", software: runtimeSoftware, ...recovery.status() },
     });
   }
   if (

package/src/local-update.mjs

@@ -1,3 +1,4 @@
+import { requireRunningSoftware } from "./software-versions.mjs";
 import { walletPackage } from "./wallet-package.mjs";
 // Apply installed packages. Preserve identity/history and startup preferences;
 // preparation failure must not enable a mismatched Wallet/Runtime pair.
@@ -185,12 +186,18 @@ export async function applyLocalUpdate({
           applied.inputs === selected.inputs &&
           applied.outputs === selected.outputs
         ) {
-          await connection({ dataDir, write });
-          phase = "unchanged";
-          write(
-            "Local installation is already up to date. Background services were not changed.",
-          );
-          return false;
+          let runningMatches = false;
+          try {
+            requireRunningSoftware(await wallet(dataDir, "status"), await runtime(dataDir), { ...pair, protocolVersion: pair.typesDependency });
+            runningMatches = true;
+          } catch { /* Keep repair available for old, stopped or unreported processes. */ }
+          if (runningMatches) {
+            await connection({ dataDir, write });
+            phase = "unchanged";
+            write("Local installation and running versions are up to date. Background services were not changed.");
+            return false;
+          }
+          write("Running versions need verification. Repair will restart the paired services.");
         }
         write(
           applied?.status === "pending"
@@ -257,10 +264,12 @@ export async function applyLocalUpdate({
               runtime(dataDir),
             ]);
             if (typeof w.locked === "boolean" && r.role === "user-runtime") {
+              requireRunningSoftware(w, r, { ...pair, protocolVersion: pair.typesDependency });
               ready = true;
               break;
             }
-          } catch {
+          } catch (error) {
+            if (error.code === "RUNNING_VERSION_UNVERIFIED") throw error;
             /* Startup can take a moment; final failure is reported below. */
           }
           await pause(500);
@@ -298,6 +307,7 @@ export async function applyLocalUpdate({
       write(
         "Service changes could not be confirmed. Check agentpay status and agentpay service logs runtime before retrying.",
       );
+    if (error.code === "RUNNING_VERSION_UNVERIFIED") write(error.message);
     const log = error.logPath || logPath;
     if (log) write("Details: " + log);
     write("After resolving the problem, run agentpay repair again.");

package/src/market-download-url.mjs

@@ -1,21 +1,26 @@
 // SPDX-License-Identifier: MPL-2.0
 // This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0.
 // If a copy was not distributed with this file, see https://mozilla.org/MPL/2.0/.
-// Preserve the approved metadata URL's ingress prefix; metadata cannot select a host.
+// The configured origin/prefix owns the download location; metadata cannot change it.
+function metadataLocation(value) {
+  const url = new URL(value);
+  const match = /^(|\/market)\/skills\/bundles\/([^/]+)(?:\/versions\/([a-f0-9]{64}))?\/metadata$/.exec(url.pathname);
+  if (url.username || url.password || url.search || url.hash || !match)
+    throw Error('MARKET_METADATA_PATH_MISMATCH');
+  return { url, prefix: match[1], service: match[2], digest: match[3] };
+}
+
+export function marketVersionMetadataUrl(source, digest) {
+  const location = metadataLocation(source);
+  if (!/^[a-f0-9]{64}$/.test(digest) || location.digest && location.digest !== digest)
+    throw Error('MARKET_PACKAGE_VERSION_MISMATCH');
+  location.url.pathname = `${location.prefix}/skills/bundles/${location.service}/versions/${digest}/metadata`;
+  return location.url;
+}
+
 export function marketDownloadUrl(metadataUrl, serviceId) {
-  const url = new URL(metadataUrl);
-  const suffix = `/skills/bundles/${encodeURIComponent(serviceId)}/metadata`;
-  if (
-    url.username ||
-    url.password ||
-    url.search ||
-    url.hash ||
-    !url.pathname.endsWith(suffix)
-  )
-    throw Error("MARKET_METADATA_PATH_MISMATCH");
-  const prefix = url.pathname.slice(0, -suffix.length);
-  if (!["", "/market"].includes(prefix))
-    throw Error("MARKET_METADATA_PREFIX_INVALID");
-  url.pathname = prefix + suffix.replace(/\/metadata$/, "/download");
+  const {url, service} = metadataLocation(metadataUrl);
+  if (service !== encodeURIComponent(serviceId)) throw Error('MARKET_METADATA_PATH_MISMATCH');
+  url.pathname = url.pathname.replace(/\/metadata$/, '/download');
   return url;
 }

package/src/official-test-package.mjs

@@ -8,8 +8,8 @@ import { createHash } from "node:crypto";
 // This belongs to the official onboarding test, never generic Runtime routing.
 export const OFFICIAL_TEST_PACKAGE = Object.freeze({
   name: "agentpay-random",
-  version: "1.2.0",
-  sha256: "aa366fc2e747b5b444786d542b0a412a505e58ea15252ac1a792b99079084146",
+  version: "1.2.1",
+  sha256: "20633b314c66166f94dc6e7d7eb5bce54ab5901fb1ed314a04ea3fd49ca8a9a4",
 });
 const mismatch = () =>
   Object.assign(

package/src/official-test-update.mjs

@@ -10,7 +10,7 @@ import {
   verifyOfficialTestBytes,
   verifyOfficialTestDigest,
 } from "./official-test-package.mjs";
-import { marketDownloadUrl } from "./market-download-url.mjs";
+import { marketDownloadUrl, marketVersionMetadataUrl } from "./market-download-url.mjs";
 
 async function localJson(path) {
   let handle;
@@ -48,6 +48,8 @@ async function download(fetchImpl, address, max) {
     redirect: "error",
     signal: AbortSignal.timeout(10000),
   });
+  if ([404, 410].includes(response.status))
+    throw Object.assign(Error("Official test version unavailable"), {code: "OFFICIAL_TEST_VERSION_UNAVAILABLE"});
   if (!response.ok || !response.body) throw Error("Market request failed");
   let length = 0;
   const chunks = [];
@@ -99,13 +101,7 @@ export async function prepareOfficialTestUpdate({
       );
       return { status: "unconfigured" };
     }
-    const metadataUrl = url(source);
-    if (
-      !/^\/(?:market\/)?skills\/bundles\/[^/]+\/metadata$/.test(
-        metadataUrl.pathname,
-      )
-    )
-      throw Error("Invalid package metadata path");
+    const metadataUrl = marketVersionMetadataUrl(url(source), OFFICIAL_TEST_PACKAGE.sha256);
     const body = JSON.parse(
       (await download(fetchImpl, metadataUrl, 65536)).toString("utf8"),
     );
@@ -150,6 +146,8 @@ export async function prepareOfficialTestUpdate({
       write(
         "Not updated: the published ZIP does not match this User release. Check for a reviewed User update; do not bypass the file check.",
       );
+    else if (error.code === "OFFICIAL_TEST_VERSION_UNAVAILABLE")
+      write("This official test version is unavailable in Market. Check for a reviewed User update or contact support; no replacement package was selected.");
     else
       write(
         "Could not prepare the official test Skill. Check your Market connection and retry agentpay repair.",

package/src/protocol-package.mjs

@@ -0,0 +1,25 @@
+// SPDX-License-Identifier: MPL-2.0
+import { createRequire } from 'node:module';
+import { readFileSync } from 'node:fs';
+import { dirname, join } from 'node:path';
+
+// Resolve from each consumer independently: npm may install a nested Protocol copy.
+// The public schema export works even when package.json is not publicly exported.
+export function installedProtocol(consumerManifest) {
+  const require = createRequire(consumerManifest);
+  let directory = dirname(require.resolve('@c4roa0/agentpay-protocol/schema'));
+  for (;;) {
+    try {
+      const pkg = JSON.parse(readFileSync(join(directory, 'package.json'), 'utf8'));
+      if (pkg.name !== '@c4roa0/agentpay-protocol' || !/^\d+\.\d+\.\d+$/.test(pkg.version)) {
+        throw Error('Installed Protocol package identity is invalid.');
+      }
+      return pkg.version;
+    } catch (error) {
+      if (error.code !== 'ENOENT') throw error;
+    }
+    const parent = dirname(directory);
+    if (parent === directory) throw Error('Installed Protocol package metadata is missing.');
+    directory = parent;
+  }
+}

package/src/software-versions.mjs

@@ -0,0 +1,48 @@
+// SPDX-License-Identifier: MPL-2.0
+import { installedProtocol } from './protocol-package.mjs';
+import { fileURLToPath } from 'node:url';
+import { readFileSync } from 'node:fs';
+
+// Capture once: installed files may be replaced while this process still runs.
+// This local compatibility report is not attestation or payment authority.
+const manifest = JSON.parse(readFileSync(new URL('../package.json', import.meta.url), 'utf8'));
+export const runtimeSoftware = Object.freeze({
+  name: '@c4roa0/agentpay-user',
+  version: manifest.version,
+  interfaceVersion: 1,
+  protocolVersion: installedProtocol(fileURLToPath(new URL('../package.json', import.meta.url))),
+});
+
+export function assessRunningSoftware(wallet, runtime, expected = {
+  userVersion: manifest.version,
+  walletVersion: manifest.dependencies['@c4roa0/agentpay-wallet'],
+  protocolVersion: manifest.dependencies['@c4roa0/agentpay-protocol'],
+}) {
+  const components = [
+    ['Wallet', wallet?.software, '@c4roa0/agentpay-wallet', expected.walletVersion],
+    ['Runtime', runtime?.software, '@c4roa0/agentpay-user', expected.userVersion],
+  ];
+  return components.map(([label, reported, name, version]) => {
+    if (!reported) return { label, state: 'unreported', expected: version };
+    const matches = reported.name === name && reported.version === version &&
+      reported.interfaceVersion === 1 && reported.protocolVersion === expected.protocolVersion;
+    return {
+      label, state: matches ? 'matched' : 'mismatch', expected: version,
+      running: typeof reported.version === 'string' && /^\d+\.\d+\.\d+$/.test(reported.version)
+        ? reported.version : 'unknown',
+    };
+  });
+}
+
+export function requireRunningSoftware(wallet, runtime, expected) {
+  const checks = assessRunningSoftware(wallet, runtime, expected);
+  const bad = checks.find(check => check.state !== 'matched');
+  if (bad) {
+    const reason = bad.state === 'unreported' ? 'does not report its running version' :
+      `does not match the installed package/interface (${bad.expected})`;
+    throw Object.assign(Error(`${bad.label} ${reason}. Update the paired packages and run agentpay repair.`), {
+      code: 'RUNNING_VERSION_UNVERIFIED',
+    });
+  }
+  return checks;
+}

package/src/status-panel.mjs

@@ -1,3 +1,4 @@
+import { assessRunningSoftware } from "./software-versions.mjs";
 import { walletCliPath } from "./wallet-package.mjs";
 // SPDX-License-Identifier: MPL-2.0
 // This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0.
@@ -172,6 +173,7 @@ export async function collectLocalStatus() {
   const value = (i) =>
     results[i].status === "fulfilled" ? results[i].value : null;
   return {
+    software: assessRunningSoftware(value(0), value(3)),
     deployment: value(6) || { state: "unknown" },
     market: value(5) || { state: "unknown" },
     authorization: value(4),
@@ -325,6 +327,13 @@ export function renderStatusPanel(
     detail =
       "Runtime is running. Order checks will continue when Wallet is available.";
     next = stopped(ws) ? "agentpay service start" : "agentpay service logs wallet";
+  } else if (model.software?.some(x => x.state !== "matched")) {
+    title = "Running software needs checking";
+    level = "wait";
+    detail = "Installed files and running processes have not been verified as a matching pair. Your original Orders are kept.";
+    next = model.software.some(x => x.state === "unreported")
+      ? "agentpay update (source checkout: update the paired packages, then agentpay repair)"
+      : "agentpay repair";
   } else if (w.policyRenewalPending) {
     title = "Spending permission renewal incomplete";
     level = "wait";
@@ -422,6 +431,11 @@ export function renderStatusPanel(
     "",
   ];
   if (!model.configurationError) {
+    if (model.software) {
+      lines.push("> Software");
+      for (const item of model.software) lines.push(`  ${badge(item.state === "matched" ? "ok" : "wait", 6)}  ${item.label.padEnd(8)}  ${item.state === "matched" ? item.running : item.state === "unreported" ? "Running version not reported" : item.running === item.expected ? "Package interface mismatch" : `Running ${item.running} · installed ${item.expected}`}`);
+      lines.push("");
+    }
     lines.push("> Services");
     const row = (label, text, state) =>
       lines.push(`  ${badge(state, 6)}  ${label.padEnd(8)}  ${text}`);

package/src/wallet-package.mjs

@@ -1,5 +1,6 @@
 // SPDX-License-Identifier: MPL-2.0
 // Resolve public Wallet entries from this User installation, never a sibling checkout.
+import { installedProtocol } from './protocol-package.mjs';
 import { createRequire } from 'node:module';
 import { readFileSync } from 'node:fs';
 import { dirname, join } from 'node:path';
@@ -17,6 +18,11 @@ export function walletPackage(userDir = userPackageDirectory) {
       manifest.dependencies?.['@c4roa0/agentpay-protocol'] !== user.dependencies?.['@c4roa0/agentpay-protocol']) {
     throw Error('Installed Wallet does not match this User version. Reinstall the reviewed User version, then run agentpay repair. Your private data is unchanged.');
   }
+  const expectedProtocol = user.dependencies['@c4roa0/agentpay-protocol'];
+  if (installedProtocol(join(userDir, 'package.json')) !== expectedProtocol ||
+      installedProtocol(manifestPath) !== expectedProtocol) {
+    throw Error('Installed Protocol does not match the reviewed User/Wallet pair. Reinstall this User version and its dependencies; private data is unchanged.');
+  }
   return { directory: dirname(manifestPath), manifest, cli: require.resolve('@c4roa0/agentpay-wallet/cli') };
 }
 export function walletCliPath(userDir) { return walletPackage(userDir).cli; }

package/update-pair.json

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