@c4roa0/agentpay-user 0.0.0-stage → 0.3.1

package/AGENTS.md

@@ -0,0 +1,137 @@
+# AgentPay User Runtime Instructions
+
+## Behavior-first verification — 2026-11-06
+
+- Prefer end-to-end tests through real product entry points and public interfaces.
+  Test observable behavior and user outcomes, not internal implementation shape.
+  Use real processes, storage and Anvil where the claim depends on them; do not
+  substitute direct database writes or internal-state injection for the workflow
+  being accepted. Controlled fixtures may prepare prerequisites.
+- Select meaningful complete journeys and failure boundaries: independent install/
+  package consumption, authorization, payment, delivery, settlement/refund, denied
+  access, duplicate requests and interrupted-operation recovery as applicable.
+  A test should demonstrate a functional requirement or a concrete regression.
+- Avoid tests that merely mirror implementation, assert source text/private helper
+  structure, or repeat the same coverage without a distinct failure boundary.
+  Syntax, type and build checks are useful checks, not functional acceptance.
+- Keep focused tests for signatures, canonical hashes, amount/time boundaries,
+  authorization and concurrency invariants when they give precise protection that
+  end-to-end tests alone cannot efficiently provide. End-to-end preference does
+  not remove negative security or financial-boundary coverage.
+- Review existing tests by the same standard. Consolidate redundant tests only
+  after equivalent meaningful coverage passes; do not delete a regression merely
+  because it is a unit test. Do not inflate test counts as a measure of readiness.
+- Label mocked external dependencies and evidence limits explicitly. Simulated
+  success does not prove real process recovery, real payment or participant usability.
+  Keep tests bounded to the change and use maintained fixtures; this principle does
+  not authorize live funds, public-network operations, destructive resets or broad
+  resource-heavy test runs.
+
+
+
+## Network portability invariant — 2026-11-04
+
+Develop and verify the same product flows on Anvil. Moving to a supported EVM
+network must use configuration, deployment artifacts and explicit signer selection,
+not a separate implementation of authorization, payment or recovery. External-owner
+signing must be testable against Anvil as well. Keep test signer guards and private
+reset/funding tools restricted; never remove them to make a product entry portable.
+Chain ID is identity, not permission to select an unlocked test signer. Network
+capabilities/finality and deployment addresses are explicit validated settings.
+Changing networks never silently rewrites saved Policies, Orders or request identity.
+Anvil results do not establish real-network compatibility or release approval.
+
+## Cache and download boundaries — 2026-11-04
+
+Cache text/files are business-neutral. Show saved Provider provenance when package
+provenance is unavailable; never infer caller identity from installed ZIPs. Merge
+matching logical outputs for display but count physical result copies. Display
+metadata must not change request identity, payment authorization or cleanup safety.
+ZIP source URLs are explicit and independent of service endpoint paths. Protocol
+v1 canonical endpoint/profile requirements remain authoritative; do not relax them
+as part of a generic installer or UI fix. Official random-test selection is scoped.
+
+
+## Canonical User commands
+
+Use grouped public commands: `wallet info/unlock/lock/restore`, `policy info/renew/revoke`,
+`service start/stop/restart`, `service autostart on/off`, `service logs wallet/runtime`,
+`market connect`, `orders ACTION ID`, `cache ACTION`, and `payment test`.
+Top-level install/setup/repair/uninstall/status/help remain. The official test is a
+paid private-Anvil check after explicit quote consent. Completed tests lead to a
+fresh quote and confirmation; unfinished tests retain their original request. Retain older test identities and records. Keep
+generated Next steps, web copy, tests and current
+runbooks aligned. Do not add legacy flat aliases. Policy owner confirmation cannot
+be bypassed by repair's `-f`. See doc/runbooks/commands.md.
+
+
+## Wallet identity priority — 2026-10-31
+
+Read `doc/reference/wallet-identity-policy-history.md` before connection/recovery work.
+Market identity is network/Module/Safe/delegate; nickname belongs to this tuple,
+while each Policy remains an independently verified Order-access scope. Do not
+merge by Safe/name alone or create device IDs. Use current progress/TODO to identify
+remaining acceptance; historical implementation pauses are not current blockers. Do not
+silently reinterpret existing connection IDs, reset data or broaden authority.
+
+
+Read `README.md`, `progress.md`, `doc/architecture.md`, `doc/design.md`, and
+`doc/TODO.md` before changing this repository. Check this repository's Git
+status first; when working inside a larger workspace, also check its enclosing
+repository status.
+
+## Product Boundary
+
+- This is the user-side Agent/Skill runtime, not the Provider server.
+- Wallet is a separate process and the only owner of the Session Key.
+- Use only Wallet's narrow AgentPay IPC operations; never add generic signing.
+- A local Skill may receive an opaque Service Authorization but must not log or
+  persist it beyond the active invocation.
+- Private request and output data travel only through User Runtime, Skill, and
+  Provider server. Settlement and Market receive only hashes and metadata.
+- Never accept caller-supplied price, usage limit, Provider identity, or payout
+  facts as authority. Settlement owns commercial truth.
+- Do not introduce legacy Execution Ticket behavior into native purchases.
+
+## Development Rules
+
+- Keep participant interactions simple: one `agentpay` command should orchestrate
+  required preparation and continue the original task. Ask only for meaningful
+  decisions or secrets; do not make users assemble build/restart/unlock commands.
+- Use concise, human-readable progress, clear completion and a concrete retry
+  action. Keep detailed diagnostics in logs, not the main guide.
+
+- Complete one approved closed loop at a time and report before starting the
+  next.
+- Native acceptance evidence must start real processes and use formal APIs. Test harnesses
+  may orchestrate and assert, but must not fabricate states through direct
+  database writes, internal stores, or static authorization bypasses.
+- Keep ports loopback-only until a later ingress decision.
+- Never commit secrets, private requests/results, runtime config, logs, or
+  generated credentials.
+- Prefer targeted syntax, unit, and process checks over full builds.
+
+## Documentation
+
+Keep `README.md`, `AGENTS.md`, `progress.md`, and the required `doc/` files
+current. Put durable evidence in `doc/records/`, runbooks in `doc/runbooks/`,
+specialized contracts in `doc/reference/`, and obsolete material in
+`doc/archive/`.
+
+## Documentation navigation
+
+Use `doc/README.md` to select documents by role and function. Keep current work in
+`progress.md` and `doc/TODO.md`; put dated verification in `doc/records/` and superseded
+chronology in `doc/archive/`. Archived pending tasks do not authorize repeating old
+operations. Keep this repository independently readable; do not link parent workspace
+documentation. Update local links and the catalog when reorganizing documents.
+
+## Public source and independent development
+
+User's original code is MPL 2.0; preserve MIT notices on Protocol and attributed
+reference fixtures. Keep private platform scripts and operational records outside
+this repository. Normal local tests need only User with `npm ci`; Wallet comes from its pinned public package;
+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.

package/CONTRIBUTING.md

@@ -0,0 +1,16 @@
+# Contributing to AgentPay User
+
+Start with the [developer guide](doc/develope.md) and [source map](doc/architecture.md).
+Explain the user-visible problem and the intended behavior before changing public
+interfaces, payment/recovery rules or persisted identity. Keep fixes focused and
+include meaningful behavioral evidence with its limits.
+
+Use disposable data and controlled local fixtures. Never add private platform source,
+real credentials, owner keys or participant records to tests. Financial changes need
+negative authorization, duplicate/conflict and recovery checks; tests of helper shape
+or source text alone are not acceptance. See the [test guide](test/README.md).
+
+Report security issues through [SECURITY.md](SECURITY.md), not a public issue.
+Contributions to MPL-covered files are provided under MPL 2.0. Preserve the separate
+licenses of vendored dependencies and attributed test fixtures. Do not submit code
+whose license or ownership you cannot grant on those terms.

package/LICENSE

@@ -0,0 +1,373 @@
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+    means each individual or legal entity that creates, contributes to
+    the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+    means the combination of the Contributions of others (if any) used
+    by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+    means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+    means Source Code Form to which the initial Contributor has attached
+    the notice in Exhibit A, the Executable Form of such Source Code
+    Form, and Modifications of such Source Code Form, in each case
+    including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+    means
+
+    (a) that the initial Contributor has attached the notice described
+        in Exhibit B to the Covered Software; or
+
+    (b) that the Covered Software was made available under the terms of
+        version 1.1 or earlier of the License, but not also under the
+        terms of a Secondary License.
+
+1.6. "Executable Form"
+    means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+    means a work that combines Covered Software with other material, in
+    a separate file or files, that is not Covered Software.
+
+1.8. "License"
+    means this document.
+
+1.9. "Licensable"
+    means having the right to grant, to the maximum extent possible,
+    whether at the time of the initial grant or subsequently, any and
+    all of the rights conveyed by this License.
+
+1.10. "Modifications"
+    means any of the following:
+
+    (a) any file in Source Code Form that results from an addition to,
+        deletion from, or modification of the contents of Covered
+        Software; or
+
+    (b) any new file in Source Code Form that contains any Covered
+        Software.
+
+1.11. "Patent Claims" of a Contributor
+    means any patent claim(s), including without limitation, method,
+    process, and apparatus claims, in any patent Licensable by such
+    Contributor that would be infringed, but for the grant of the
+    License, by the making, using, selling, offering for sale, having
+    made, import, or transfer of either its Contributions or its
+    Contributor Version.
+
+1.12. "Secondary License"
+    means either the GNU General Public License, Version 2.0, the GNU
+    Lesser General Public License, Version 2.1, the GNU Affero General
+    Public License, Version 3.0, or any later versions of those
+    licenses.
+
+1.13. "Source Code Form"
+    means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+    means an individual or a legal entity exercising rights under this
+    License. For legal entities, "You" includes any entity that
+    controls, is controlled by, or is under common control with You. For
+    purposes of this definition, "control" means (a) the power, direct
+    or indirect, to cause the direction or management of such entity,
+    whether by contract or otherwise, or (b) ownership of more than
+    fifty percent (50%) of the outstanding shares or beneficial
+    ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+    Licensable by such Contributor to use, reproduce, make available,
+    modify, display, perform, distribute, and otherwise exploit its
+    Contributions, either on an unmodified basis, with Modifications, or
+    as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+    for sale, have made, import, and otherwise transfer either its
+    Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+    or
+
+(b) for infringements caused by: (i) Your and any other third party's
+    modifications of Covered Software, or (ii) the combination of its
+    Contributions with other software (except as part of its Contributor
+    Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+    its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+    Form, as described in Section 3.1, and You must inform recipients of
+    the Executable Form how they can obtain a copy of such Source Code
+    Form by reasonable means in a timely manner, at a charge no more
+    than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+    License, or sublicense it under different terms, provided that the
+    license for the Executable Form does not attempt to limit or alter
+    the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+*                                                                      *
+*  6. Disclaimer of Warranty                                           *
+*  -------------------------                                           *
+*                                                                      *
+*  Covered Software is provided under this License on an "as is"       *
+*  basis, without warranty of any kind, either expressed, implied, or  *
+*  statutory, including, without limitation, warranties that the       *
+*  Covered Software is free of defects, merchantable, fit for a        *
+*  particular purpose or non-infringing. The entire risk as to the     *
+*  quality and performance of the Covered Software is with You.        *
+*  Should any Covered Software prove defective in any respect, You     *
+*  (not any Contributor) assume the cost of any necessary servicing,   *
+*  repair, or correction. This disclaimer of warranty constitutes an   *
+*  essential part of this License. No use of any Covered Software is   *
+*  authorized under this License except under this disclaimer.         *
+*                                                                      *
+************************************************************************
+
+************************************************************************
+*                                                                      *
+*  7. Limitation of Liability                                          *
+*  --------------------------                                          *
+*                                                                      *
+*  Under no circumstances and under no legal theory, whether tort      *
+*  (including negligence), contract, or otherwise, shall any           *
+*  Contributor, or anyone who distributes Covered Software as          *
+*  permitted above, be liable to You for any direct, indirect,         *
+*  special, incidental, or consequential damages of any character      *
+*  including, without limitation, damages for lost profits, loss of    *
+*  goodwill, work stoppage, computer failure or malfunction, or any    *
+*  and all other commercial damages or losses, even if such party      *
+*  shall have been informed of the possibility of such damages. This   *
+*  limitation of liability shall not apply to liability for death or   *
+*  personal injury resulting from such party's negligence to the       *
+*  extent applicable law prohibits such limitation. Some               *
+*  jurisdictions do not allow the exclusion or limitation of           *
+*  incidental or consequential damages, so this exclusion and          *
+*  limitation may not apply to You.                                    *
+*                                                                      *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+  This Source Code Form is subject to the terms of the Mozilla Public
+  License, v. 2.0. If a copy of the MPL was not distributed with this
+  file, You can obtain one at https://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+  This Source Code Form is "Incompatible With Secondary Licenses", as
+  defined by the Mozilla Public License, v. 2.0.

package/NOTICE.md

@@ -0,0 +1,20 @@
+# Licensing and third-party material
+
+AgentPay User's original source and documentation are licensed under the Mozilla
+Public License 2.0; see LICENSE. This Source Code Form is subject to the terms of
+the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with
+this file, You can obtain one at https://mozilla.org/MPL/2.0/.
+
+Exceptions retain their own licenses:
+
+- `@c4roa0/agentpay-protocol`: public npm dependency, MIT; its license ships
+  with the installed package. This does not include private Settlement source.
+- `test/fixtures/skill-zip.mjs` and `test/fixtures/random-skill/`: reference fixture
+  snapshot from AgentPay Agent, MIT; see `test/fixtures/REFERENCE-SKILL-LICENSE`
+  and its README for the source revision.
+- Installed third-party packages retain the licenses shipped with those packages.
+  `@c4roa0/agentpay-wallet` is a separate MIT-licensed package; its license ships
+  with the installed dependency and it is not relicensed by User.
+
+For license interpretation, consult the unmodified license text and Mozilla's FAQ:
+https://www.mozilla.org/en-US/MPL/2.0/FAQ/.

package/README.md

@@ -1,3 +1,86 @@
-# Temporary Holding Version
+# AgentPay User
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+User connects your AI Agent's Skills to paid services. A separate local Wallet
+holds the Session Key; your Safe's bounded permission controls spending. After
+setup, eligible purchases do not require an owner-wallet signature every time.
+
+User is the Agent/Skill runtime, not a Provider server or a general-purpose wallet.
+It retains request identity and local results so interruptions can be recovered
+without silently creating a replacement purchase.
+
+## Install with npm
+
+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.1
+agentpay install --market https://YOUR_MARKET_ORIGIN
+```
+
+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.
+
+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
+private key into AgentPay. See [installation and first use](doc/runbooks/user-onboarding.md).
+
+Program files and private state are separate. Keys, Policies, Orders and cache
+normally live in `~/.local/share/agentpay/user`; an existing custom data directory
+is retained. Installation checkpoints use `~/.local/state/agentpay/user` (or
+`$XDG_STATE_HOME/agentpay/user`). Upgrading program files does not erase either.
+
+## After setup
+
+```sh
+agentpay status
+agentpay wallet unlock
+agentpay orders list
+agentpay market connect
+```
+
+Linux background services use your systemd user session. Wallet starts locked after
+a restart. `agentpay service help` explains startup, stop and logs; `agentpay help` lists
+all groups. Global npm installations use `agentpay update` to review and install a
+new User version with its matching Wallet and official test Skill. Source checkouts
+update their files, run `npm ci`, then `agentpay repair`. [Commands](doc/runbooks/commands.md) · [Updates](doc/runbooks/local-update.md)
+· [Backup and restore](doc/runbooks/wallet-identity.md).
+
+## 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.
+- [Contribution guide](CONTRIBUTING.md), [documentation catalog](doc/README.md),
+  [progress](progress.md) and [TODO](doc/TODO.md).
+
+## Safety and scope
+
+Source includes external-owner browser approval and a guarded Anvil test signer.
+Network identity never automatically selects the test signer. The recorded private
+single-owner journey is not real-network, multisig or production acceptance.
+Current release gates are in TODO. macOS startup remains unverified.
+
+Keep keys, passwords, caller tokens and private Order data out of repositories and
+support messages. For a suspected compromise, follow
+[emergency payment stop](doc/runbooks/emergency-payment-stop.md) from a trusted device.
+Locking Wallet or disconnecting Market does not revoke on-chain spending permission.
+
+Original User code is **MPL 2.0**. See [LICENSE](LICENSE), [third-party notices](NOTICE.md)
+and [security reporting](SECURITY.md). Wallet and Protocol retain their own licenses.

package/SECURITY.md

@@ -0,0 +1,16 @@
+# Security reports
+
+Report suspected vulnerabilities privately to **agentpay@mail.c4r.fun**. Include
+User/Wallet versions, the affected interface and reproducible steps using disposable
+data. Do not post keys, passwords, tokens, signed payments or private Order inputs
+in public issues. Do not send them to support either.
+
+User Runtime coordinates purchases; Wallet owns the Session Key and Safe enforces
+on-chain permission. A local caller token is not a sandbox against code running
+as the same operating-system user. Private Anvil tests do not establish real-funds
+safety or a completed security audit.
+
+If a key or computer may be compromised, use a trusted device and your Safe owner
+wallet to stop payment permission. See [emergency instructions](doc/runbooks/emergency-payment-stop.md).
+Deleting User, disconnecting Market or stopping a process does not revoke on-chain
+authorization.