@maxceem/agw 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Maksym Mykhailenko
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,63 @@
+# App AI Gateway CLI
+
+The `@maxceem/agw` package provides the `agw` executable. Node.js 22.19 or newer is required. It includes the compatible gateway release and Wrangler toolchain; end users do not need Git, pnpm, a global Wrangler installation, or a repository checkout.
+
+```sh
+npx @maxceem/agw provider add --type openai
+npx @maxceem/agw app add --type ios --team-id ABCDE12345 --bundle-id com.example.app
+```
+
+A fresh cloud connection creates your account only when adding a provider, provider gateway, or application. Help, lists, status, validation and dry runs never create accounts. Logout retains your selected deployment and prior account marker; invalid or revoked access requires login, with no automatic fallback or second account.
+
+For automation, have a human supply a provider credential in their own browser:
+
+```sh
+agw provider add --type openai --browser --no-open --json
+agw operation wait <operation-id> --timeout 300 --json
+```
+
+Share both the returned URL and human confirmation code where present. Hidden terminal input only prevents echo; an agent controlling that terminal can still observe it. The browser must be outside the agent's observable browser surface for credential isolation. Never pass credentials as command arguments. `--key-stdin` explicitly reads a single secret line. `--no-input` prohibits terminal prompts, and `--no-open` returns a browser operation without waiting.
+
+Run `agw --help` for the complete command surface and `agw <group> <command> --help` for its flags. Resource IDs and slugs are exact; display names are not selectors. File outputs never overwrite existing files. Server application keys are written with mode 0600 and never included in stdout. If persistence fails, the CLI attempts immediate revocation and reports the key ID for recovery.
+
+Application JSON uses the gateway's shared complete write schema (`name`, `config`, optional `status`). Derive an editable definition from a saved app with `agw app show <app-id> --json | jq '.result.app | {name, config, status}'`; `app validate --file` and `app add --file --dry-run` validate it without account creation. Offline validation reports skipped remote checks. File mode preserves omission of App Attest environments; the simple iOS flags explicitly enable production and development. Application updates require the original ETag in `If-Match`; conflicting edits return an error instead of overwriting changes. Retained selected providers keep their detailed policies.
+
+Swift snippets use the current package at `https://github.com/maxceem/app-ai-gateway-swift` (from version 1.0.0), actual application/provider IDs, and the saved authentication mode. Issuer examples require replacing the indicated identity SDK call. Requests still need a provider-native body and must be sent by the caller. No setup or readiness check sends paid inference or proves physical-device attestation.
+
+## Output and state
+
+`--json` emits exactly one JSON document to stdout. Progress goes to stderr. The result envelope is `{schemaVersion:1,ok:true,context:{url,accountId?,deploymentId?},result}`. Errors are `{schemaVersion:1,ok:false,error:{code,message,nextAction,details?}}`. Unknown remote fields are excluded from output; complete validated application config preserves provider-native endpoint parameters.
+
+Exit statuses: `0` success (including pending handoff initiation), `2` input/validation error, `3` remote/connectivity or failed handoff, `4` local state/recovery/authentication issue, `5` wait timeout. Timeout includes still-pending operation metadata and does not cancel or extend the server operation. Poll authorization is stored separately from public operation IDs/URLs. Authentication handoff completion is persisted before output, and replay cannot undo a logout or later connection switch.
+
+State is `$XDG_STATE_HOME/agw` or `~/.local/state/agw` on Unix, and `%LOCALAPPDATA%/agw` on Windows. The directory is mode 0700 and files are mode 0600. It contains one active connection, the previous connection for intentional recovery, pending operations, creation retry proofs, application keys, and protected installation journals. No public profile selectors or gateway credential environment overrides exist. Back up this directory securely. Concurrent commands use an exclusive lock; after a crashed process, inspect the PID in `connection.lock` before removing that lock. Never delete connection state merely to resolve an authentication error.
+
+Public API URLs require HTTPS, no userinfo, query, fragment or path. Only `localhost`, `127.0.0.1` and `[::1]` permit HTTP for local development. Authenticated HTTP redirects are refused. Connecting authenticates only to the requested origin and selects it after success.
+
+## Self-hosting
+
+```sh
+agw deployment setup --name my-gateway --no-domain
+agw deployment update --dry-run
+agw deployment domain --hostname ai.example.com --dry-run
+```
+
+Setup obtains Cloudflare authorization using bundled Wrangler OAuth, or accepts standard securely configured Cloudflare credentials such as `CLOUDFLARE_API_TOKEN`. If more than one Cloudflare account is accessible, choose one with `--cloudflare-account-id`. Noninteractive mutations require explicit configuration and `--yes`; `--yes` does not grant Cloudflare permissions or approve browser identity ceremonies.
+
+The npm package contains a versioned Worker bundle, console assets, migrations, configuration, and SHA-256 manifest. npm package integrity authenticates the package; local manifest/file digests detect corrupt assets before deployment. `--version` selects only the bundled compatible release; use the matching CLI package version for another release. No unversioned source download or arbitrary downgrade is performed. Release format/schema versions are checked before mutation.
+
+Installation journals are written before creating resources, keep generated vault/signing/bootstrap secrets across retries, and bind the Cloudflare account, Worker, D1 database and immutable deployment ID. A Worker name collision never authorizes takeover. Retry an incomplete setup with the same name/account; its previous active gateway connection remains selected until bootstrap succeeds. A completed setup does not replay retired bootstrap credentials or overwrite subsequently rotated secrets. Updates preserve existing secrets and reject unsupported schema transitions. Database migrations do not have an automatic rollback.
+
+A URL-only connection can be matched interactively to an explicitly selected accessible Worker only when its Cloudflare `DEPLOYMENT_ID` matches the gateway. Unsupported extra resource bindings fail rather than being discarded. Noninteractive deployment administration needs the existing installation journal. Dry runs discover/validate only; they do not provision resources, generate/upload secrets, change DNS, bootstrap accounts or select connections.
+
+Custom domains require an accessible active zone. Existing unrelated DNS or Worker domain attachments are refused. The new endpoint must identify the same deployment before credentials follow it. Existing hostnames remain served; mobile applications keep their embedded URL until updated. Changing from cloud to self-hosting does not migrate app IDs, provider credentials, usage or existing applications.
+
+## Release verification for contributors
+
+`pnpm run cli:check` type-checks the CLI with `tsgo` and then bundles the portable schemas and executable. `pnpm run cli:test` runs parser, state, transport, command and mocked deployment tests; both are included in root verification. `pnpm --filter @maxceem/agw release:build` builds the actual deployable bundle locally. `npm pack` runs that release build and packages only `dist`, this README and the Apache-2.0 license. Verify the tarball and invoke its installed executable outside the repository before publishing. Publishing and live Cloudflare operations are separate release decisions.
+
+Creation retries persist a request proof before sending provider, gateway, app or application-key creation. Repeating an unfinished saved request returns its original result. After successful output delivery, its local pending receipt is acknowledged, so a later invocation is a new intentional creation. A server key response can be recovered remotely for 15 minutes; after that, the error identifies the existing resource so you can inspect and replace its key intentionally. Non-secret receipt records prevent duplicate creation for the lifetime of the account. An unfinished local request older than 90 days refuses to submit again automatically.
+
+The CLI saves a one-time key response in protected local state before writing the selected `--key-output` file. If the file write fails, repeat the same command to complete that file, or choose a new unused output path; this uses the saved active key and does not mint another. Once file delivery completes, the recovery copy is removed; a retry before successful command output verifies that original file. After stdout delivery is acknowledged, a later key creation is a new request and requires a new unused output file. Existing unrelated files and replaced output reservations are never overwritten.
+
+Unfinished bootstrap attempts also have a 90-day local retry deadline. Missing or expired timestamps fail closed and preserve the proof for recovery. Server cleanup retains only a non-secret, proof-bound bootstrap tombstone after deleting an expired account, so an old retry cannot recreate that account. The tombstone contains no account identity or credential and is intentionally retained beyond ordinary challenge expiry.