@simonsbs/keylore 1.0.0-rc4

package/.env.example

@@ -0,0 +1,64 @@
+KEYLORE_DATABASE_URL=postgresql://keylore:keylore@127.0.0.1:5432/keylore
+KEYLORE_DATABASE_POOL_MAX=10
+KEYLORE_AUTH_CLIENTS_FILE=auth-clients.json
+KEYLORE_LOCAL_SECRETS_FILE=local-secrets.enc.json
+KEYLORE_LOCAL_SECRETS_KEY_FILE=local-secrets.key
+KEYLORE_HTTP_HOST=127.0.0.1
+KEYLORE_HTTP_PORT=8787
+KEYLORE_PUBLIC_BASE_URL=http://127.0.0.1:8787
+KEYLORE_OAUTH_ISSUER_URL=http://127.0.0.1:8787/oauth
+KEYLORE_DEFAULT_PRINCIPAL=local-operator
+KEYLORE_ENVIRONMENT=development
+KEYLORE_LOG_LEVEL=info
+KEYLORE_BOOTSTRAP_FROM_FILES=true
+KEYLORE_MAX_REQUEST_BYTES=131072
+KEYLORE_OUTBOUND_TIMEOUT_MS=10000
+KEYLORE_MAX_RESPONSE_BYTES=32768
+KEYLORE_RATE_LIMIT_WINDOW_MS=60000
+KEYLORE_RATE_LIMIT_MAX_REQUESTS=120
+KEYLORE_MAINTENANCE_ENABLED=true
+KEYLORE_MAINTENANCE_INTERVAL_MS=60000
+KEYLORE_ACCESS_TOKEN_TTL_SECONDS=3600
+KEYLORE_AUTHORIZATION_CODE_TTL_SECONDS=300
+KEYLORE_REFRESH_TOKEN_TTL_SECONDS=2592000
+KEYLORE_APPROVAL_TTL_SECONDS=1800
+KEYLORE_APPROVAL_REVIEW_QUORUM=1
+KEYLORE_BREAKGLASS_MAX_DURATION_SECONDS=900
+KEYLORE_BREAKGLASS_REVIEW_QUORUM=1
+KEYLORE_VAULT_ADDR=
+KEYLORE_VAULT_TOKEN=
+KEYLORE_VAULT_NAMESPACE=
+KEYLORE_OP_BIN=op
+KEYLORE_AWS_BIN=aws
+KEYLORE_GCLOUD_BIN=gcloud
+KEYLORE_EGRESS_ALLOW_PRIVATE_IPS=false
+KEYLORE_EGRESS_ALLOWED_HOSTS=
+KEYLORE_EGRESS_ALLOWED_HTTPS_PORTS=443
+KEYLORE_SANDBOX_INJECTION_ENABLED=false
+KEYLORE_SANDBOX_COMMAND_ALLOWLIST=
+KEYLORE_SANDBOX_ENV_ALLOWLIST=
+KEYLORE_SANDBOX_DEFAULT_TIMEOUT_MS=5000
+KEYLORE_SANDBOX_MAX_OUTPUT_BYTES=16384
+KEYLORE_ADAPTER_MAX_ATTEMPTS=2
+KEYLORE_ADAPTER_RETRY_DELAY_MS=250
+KEYLORE_ADAPTER_CIRCUIT_BREAKER_THRESHOLD=3
+KEYLORE_ADAPTER_CIRCUIT_BREAKER_COOLDOWN_MS=60000
+KEYLORE_NOTIFICATION_WEBHOOK_URL=
+KEYLORE_NOTIFICATION_SIGNING_SECRET=
+KEYLORE_NOTIFICATION_TIMEOUT_MS=5000
+KEYLORE_TRACE_CAPTURE_ENABLED=true
+KEYLORE_TRACE_RECENT_SPAN_LIMIT=500
+KEYLORE_TRACE_EXPORT_URL=
+KEYLORE_TRACE_EXPORT_AUTH_HEADER=
+KEYLORE_TRACE_EXPORT_BATCH_SIZE=20
+KEYLORE_TRACE_EXPORT_INTERVAL_MS=1000
+KEYLORE_TRACE_EXPORT_TIMEOUT_MS=5000
+KEYLORE_ROTATION_PLANNING_HORIZON_DAYS=14
+
+# Demo credentials. These are references only; KeyLore never stores secret values in the catalogue.
+KEYLORE_SECRET_GITHUB_READONLY=
+KEYLORE_SECRET_NPM_READONLY=
+
+# Bootstrap OAuth clients. Required when bootstrapping auth clients from data/auth-clients.json.
+KEYLORE_BOOTSTRAP_ADMIN_CLIENT_SECRET=
+KEYLORE_BOOTSTRAP_CONSUMER_CLIENT_SECRET=

package/LICENSE

@@ -0,0 +1,176 @@
+                                 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

package/NOTICE

@@ -0,0 +1,5 @@
+KeyLore
+Copyright 2026 Simon
+
+This product includes third-party open source software distributed under
+their own licenses. Dependency metadata is captured in `package-lock.json`.

package/README.md

@@ -0,0 +1,424 @@
+# KeyLore
+
+KeyLore is a credential broker and searchable credential catalogue for MCP clients such as Codex CLI, Claude Code, and other Model Context Protocol toolchains.
+
+The design goal comes directly from the local `KeyLore.md` production spec used to bootstrap this repository: let agents discover and use the right credential metadata without ever putting secret values into model context, prompts, logs, or tool results.
+
+## Status
+
+This repository is incubating privately today, but it is structured to be published as open source without a cleanup pass. The repo already includes:
+
+- an Apache-2.0 project license and `NOTICE`
+- contributor and security policies
+- CI, container packaging, and deployment examples
+- architecture, API, threat model, and roadmap docs
+- conformance and tenant-operations guides
+- compatibility contract and release-hardening guides
+- admin UI guide
+- release checklist
+
+## What is implemented now
+
+- MCP server for `stdio` and Streamable HTTP
+- metadata-only catalogue search and retrieval tools
+- default-deny policy engine with domain and operation constraints
+- PostgreSQL-backed catalogue, policy, and audit persistence with startup migrations
+- OAuth-style client credentials token issuance for remote HTTP and MCP access
+- PKCE-bound `authorization_code` plus rotating `refresh_token` support for interactive public or confidential clients
+- protected-resource metadata for REST and MCP surfaces
+- identity-aware policy evaluation with role-aware rule matching
+- approval-required policy outcomes with review endpoints and CLI support
+- multi-review approval and break-glass quorums with duplicate-review protection
+- RBAC separation for admin, auth admin, operator, maintenance, backup, break-glass, auditor, approver, and consumer clients
+- policy simulation and non-executing dry-run access evaluation
+- auth-client lifecycle APIs with secret rotation and status control
+- token listing and explicit token revocation APIs
+- pluggable secret adapters for environment bindings, Vault, 1Password, AWS Secrets Manager, and GCP Secret Manager
+- catalog reporting for rotation and expiry visibility
+- sandboxed injection mode for tightly allowlisted compatibility commands
+- constrained proxy execution for `http.get` and `http.post`
+- HTTP admin/API surface for catalogue search, access requests, approvals, audit reads, adapter health, runtime injection, and auth-client inspection
+- local admin CLI for catalogue, reporting, access evaluation, runtime injection, approvals, auth-client, maintenance, and backup operations
+- request-size limits, database-backed rate limiting, background maintenance cleanup, outbound timeouts, and response-size caps
+- Prometheus-style `/metrics` telemetry and request correlation headers for operational visibility
+- audited break-glass request, approval, revoke, and emergency-use flow
+- delegated backup export, inspect, and restore API endpoints for self-hosted operators
+- egress policy blocks private, loopback, and link-local upstream targets unless explicitly allowed
+- sandbox env allowlisting for injected runtime execution
+- signed notification webhooks for approval and break-glass lifecycle events
+- request trace capture with `x-trace-id` propagation and recent-trace inspection
+- optional external trace export with operator status and manual flush controls
+- `private_key_jwt` OAuth client authentication with assertion replay protection
+- persisted credential rotation workflows with plan, start, complete, and fail transitions
+- tenant-aware partitioning for credentials, policies, auth clients, approvals, break-glass, audit events, tokens, rotation runs, and logical backups
+- first-class tenant registry with tenant bootstrap workflows for auth-client seeding
+- tenant-scoped backup export and restore isolation for delegated tenant operators
+- explicit conformance suite for auth, tenancy, and backup boundary regressions
+- frozen `v1.0.0-rc1` compatibility contract for OAuth, REST, and MCP tool names
+- dedicated hardening suite for replay, tenant-isolation, and delegated-admin abuse paths
+- minimal admin UI for operator login, tenants, auth clients, reviews, backups, audit, and system status
+- Helm chart with dev, staging, and production values profiles
+- HA-oriented Helm profile with pod disruption budget and spread controls
+- tagged release workflow with SBOM generation, vulnerability scanning, keyless image signing, and Helm upgrade validation
+- shipped Grafana dashboard and Prometheus alert rule examples
+
+## What is intentionally deferred
+
+The full `KeyLore.md` specification is broader than a sane `v1.0.0-rc4` delivery. The main remaining work before `v1.0.0` is:
+
+- public release polish and final operator documentation cleanup
+
+Those items are tracked in [docs/roadmap.md](/home/simon/keylore/docs/roadmap.md) and mapped back to the spec in [docs/keylore-spec-map.md](/home/simon/keylore/docs/keylore-spec-map.md).
+
+The active post-`v1.0.0-rc4` refocus is documented in [docs/core-mode-plan.md](/home/simon/keylore/docs/core-mode-plan.md): make the default user journey "add secret, add context, connect MCP, use it" and push broader operator features behind an advanced path.
+
+The handoff from local core mode to advanced self-hosted mode is documented in [docs/production-handoff.md](/home/simon/keylore/docs/production-handoff.md).
+
+## Quick start
+
+1. Install dependencies:
+
+```bash
+npm install
+```
+
+2. Start the zero-config local stack:
+
+```bash
+npm run quickstart
+```
+
+For a clean Linux VM install from npm instead of cloning the repo:
+
+```bash
+npm install -g @simonsbs/keylore@next
+keylore-http
+```
+
+That starts KeyLore from the packaged migrations and seed data, while writable state defaults to `~/.keylore`.
+
+To simulate a brand-new user install on the same machine without reusing your normal checkout or shell environment:
+
+```bash
+npm run ops:fresh-user-env
+```
+
+That launches an isolated disposable user, a fresh clone, and a separate KeyLore UI port for onboarding and MCP testing. By default it clones from the current local repo source so it also works while the repo is private.
+
+This starts local PostgreSQL, waits for readiness, and boots KeyLore at `http://127.0.0.1:8787`.
+If KeyLore is already running locally on that port, the command reuses the existing instance instead of failing.
+
+3. Open KeyLore in your browser:
+
+`http://127.0.0.1:8787/`
+
+KeyLore now redirects `/` to `/admin` and automatically opens a local operator session on loopback development installs.
+
+If that local session bootstrap fails for any reason, use `Start working locally` or the manual sign-in form shown on the page.
+
+4. In `Save token`, choose the closest template for the token you are adding, such as `GitHub read-only`, `GitHub write-capable`, `npm read-only`, or `Internal service token`, then fill in:
+- `Name shown in KeyLore`
+- `Token key`
+- `Paste token`
+- `Where can it be used?`
+- `Tell the AI when to use this token`
+
+That stores the raw token outside the searchable catalogue and keeps only the LLM-facing metadata in the credential record.
+
+5. Review `Writing help` and `What the AI will see` in the form to confirm the agent-facing record is specific, useful, and secret-free. `Token key` is the unique identifier for the token; if KeyLore says a token already exists, change that field and save again. Open `Advanced token settings` only if you need to change storage mode, risk level, service name, tags, or write access.
+
+6. In `Saved tokens`, look under `Your tokens` for the ones you added yourself. `Included examples` are seeded local records and are shown separately so they do not get confused with your own tokens.
+
+7. In `Test credential`, choose `Token to check`, set the `URL to call with this token`, and run the check.
+
+The check makes a real brokered `http.get` call with that token and URL. Success means the token, the target domain, and KeyLore policy all allowed the request.
+
+8. In `Connect your AI tool`, copy the generated Codex or Gemini CLI local snippet for the easiest setup. Use the built-in `First prompt to try` examples after you restart the client. If you want remote HTTP MCP instead, open `Remote or advanced connection options` and mint an `/mcp` token there.
+
+Everything beyond that now sits behind `Show advanced controls` in the UI, so a first-run user can ignore tenants, OAuth client administration, approvals, backups, audit, and system internals entirely.
+
+After creation, use `Inspect or edit AI-facing context` inside `Save token` if you need to refine the metadata without re-entering or exposing the stored secret. Saved token cards also support lightweight lifecycle actions such as rename, retag, and archive/restore under `More actions`.
+
+When that local path stops being enough, use [docs/production-handoff.md](/home/simon/keylore/docs/production-handoff.md) to decide when to switch to external secret backends, real OAuth clients, approvals, and tenant-separated self-hosting.
+
+## Optional local overrides
+
+If you want to override the local defaults, create `.env` from [.env.example](/home/simon/keylore/.env.example). KeyLore now auto-loads `.env` on startup, so you do not need to `source` it manually.
+
+If you override `KEYLORE_BOOTSTRAP_ADMIN_CLIENT_SECRET`, the local admin quickstart button is no longer shown in the UI. At that point you are expected to sign in with your configured client credentials.
+
+Common overrides:
+
+```bash
+cp .env.example .env
+```
+
+```bash
+KEYLORE_SECRET_GITHUB_READONLY=...
+KEYLORE_SECRET_NPM_READONLY=...
+KEYLORE_BOOTSTRAP_ADMIN_CLIENT_SECRET=...
+KEYLORE_BOOTSTRAP_CONSUMER_CLIENT_SECRET=...
+KEYLORE_SANDBOX_INJECTION_ENABLED=true
+KEYLORE_SANDBOX_COMMAND_ALLOWLIST=/usr/bin/env,node
+```
+
+## Advanced local usage
+
+Start PostgreSQL only:
+
+```bash
+npm run db:up
+```
+
+Start the HTTP server directly:
+
+```bash
+npm run dev:http
+```
+
+Or run KeyLore as a local stdio MCP server:
+
+```bash
+npm run dev:stdio
+```
+
+Use the local CLI:
+
+```bash
+npm run dev:cli -- catalog list
+```
+
+Mint an access token for the REST API:
+
+```bash
+curl -X POST http://127.0.0.1:8787/oauth/token \
+  -H 'content-type: application/x-www-form-urlencoded' \
+  -d 'grant_type=client_credentials&client_id=keylore-admin-local&client_secret=REPLACE_ME&scope=catalog:read%20broker:use%20approval:read%20approval:review%20audit:read%20auth:read%20auth:write%20system:read%20system:write%20backup:read%20backup:write%20breakglass:request%20breakglass:read%20breakglass:review%20sandbox:run&resource=http://127.0.0.1:8787/v1'
+```
+
+Remote tokens are tenant-scoped through their OAuth client. A tenant-bound caller only sees and mutates records from its own tenant; the local CLI continues to run as a global operator.
+
+Interactive flows can mint a user-bound code with `POST /oauth/authorize`, then exchange it at `POST /oauth/token` with `grant_type=authorization_code` and PKCE.
+
+Verify the health endpoint:
+
+```bash
+curl http://127.0.0.1:8787/healthz
+```
+
+Inspect metrics and maintenance status:
+
+```bash
+curl http://127.0.0.1:8787/metrics
+npm run dev:cli -- system maintenance
+npm run dev:cli -- system traces --limit 10
+npm run dev:cli -- system trace-exporter
+npm run dev:cli -- system rotations list
+```
+
+Validate the Helm deployment path:
+
+```bash
+npm run ops:helm-validate
+```
+
+Run the release candidate gates:
+
+```bash
+npm run ops:release-verify
+```
+
+Open the admin UI in a browser at `http://127.0.0.1:8787/admin`.
+
+## Example API usage
+
+Search the catalogue:
+
+```bash
+TOKEN=...
+curl -X POST http://127.0.0.1:8787/v1/catalog/search \
+  -H "authorization: Bearer ${TOKEN}" \
+  -H 'content-type: application/json' \
+  -d '{"query":"github","limit":5}'
+```
+
+Simulate an access request without executing it:
+
+```bash
+TOKEN=...
+curl -X POST http://127.0.0.1:8787/v1/access/simulate \
+  -H "authorization: Bearer ${TOKEN}" \
+  -H 'content-type: application/json' \
+  -d '{
+    "credentialId":"github-readonly-demo",
+    "operation":"http.get",
+    "targetUrl":"https://api.github.com/repos/modelcontextprotocol/specification"
+  }'
+```
+
+Read rotation and expiry status:
+
+```bash
+TOKEN=...
+curl http://127.0.0.1:8787/v1/catalog/reports \
+  -H "authorization: Bearer ${TOKEN}"
+```
+
+Request a proxy call:
+
+```bash
+TOKEN=...
+curl -X POST http://127.0.0.1:8787/v1/access/request \
+  -H "authorization: Bearer ${TOKEN}" \
+  -H 'content-type: application/json' \
+  -d '{
+    "credentialId":"github-readonly-demo",
+    "operation":"http.get",
+    "targetUrl":"https://api.github.com/repos/modelcontextprotocol/specification"
+  }'
+```
+
+Run a tightly allowlisted injected command:
+
+```bash
+TOKEN=...
+curl -X POST http://127.0.0.1:8787/v1/runtime/sandbox \
+  -H "authorization: Bearer ${TOKEN}" \
+  -H 'content-type: application/json' \
+  -d '{
+    "credentialId":"github-readonly-demo",
+    "command":"node",
+    "args":["-e","console.log(process.env.GITHUB_TOKEN)"]
+  }'
+```
+
+Inspect recent traces for a propagated request trace id:
+
+```bash
+TOKEN=...
+curl "http://127.0.0.1:8787/v1/system/traces?traceId=deploy-trace-123&limit=10" \
+  -H "authorization: Bearer ${TOKEN}"
+```
+
+Inspect the external trace-export pipeline:
+
+```bash
+TOKEN=...
+curl http://127.0.0.1:8787/v1/system/trace-exporter \
+  -H "authorization: Bearer ${TOKEN}"
+curl -X POST http://127.0.0.1:8787/v1/system/trace-exporter/flush \
+  -H "authorization: Bearer ${TOKEN}"
+```
+
+Bootstrap a tenant and interactive client seed set:
+
+```bash
+npm run dev:cli -- tenants bootstrap --file ./tenant-bootstrap.json
+```
+
+Plan rotation runs:
+
+```bash
+TOKEN=...
+curl -X POST http://127.0.0.1:8787/v1/system/rotations/plan \
+  -H "authorization: Bearer ${TOKEN}" \
+  -H 'content-type: application/json' \
+  -d '{"horizonDays":14}'
+```
+
+## Example Codex configuration
+
+See [examples/codex/config.toml](/home/simon/keylore/examples/codex/config.toml) for both `stdio` and remote HTTP MCP registration examples. For remote MCP, mint a token with `resource=http://127.0.0.1:8787/mcp` and export it into the configured client env var.
+
+## CLI examples
+
+List the catalogue:
+
+```bash
+npm run dev:cli -- catalog list
+```
+
+Search the catalogue:
+
+```bash
+npm run dev:cli -- catalog search --query github --limit 5
+```
+
+Read recent audit events:
+
+```bash
+npm run dev:cli -- audit recent --limit 10
+```
+
+Inspect trace-export status:
+
+```bash
+npm run dev:cli -- system trace-exporter
+npm run dev:cli -- system trace-exporter flush
+```
+
+Work rotation runs:
+
+```bash
+npm run dev:cli -- system rotations list
+npm run dev:cli -- system rotations plan --horizon-days 14
+```
+
+Simulate a request locally:
+
+```bash
+npm run dev:cli -- access simulate --file ./request.json
+```
+
+Inspect rotation status locally:
+
+```bash
+npm run dev:cli -- catalog report
+```
+
+Create a logical backup locally:
+
+```bash
+npm run dev:cli -- system backup create --file ./keylore-backup.json
+```
+
+Run the restore drill locally:
+
+```bash
+KEYLORE_DATABASE_URL=postgresql://... \
+KEYLORE_BOOTSTRAP_ADMIN_CLIENT_SECRET=... \
+KEYLORE_BOOTSTRAP_CONSUMER_CLIENT_SECRET=... \
+npm run ops:restore-drill
+```
+
+Validate Helm render and dry-run upgrade paths:
+
+```bash
+npm run ops:helm-validate
+```
+
+## Documentation
+
+- [docs/architecture.md](/home/simon/keylore/docs/architecture.md)
+- [docs/api.md](/home/simon/keylore/docs/api.md)
+- [docs/deployment.md](/home/simon/keylore/docs/deployment.md)
+- [docs/configuration.md](/home/simon/keylore/docs/configuration.md)
+- [docs/cli.md](/home/simon/keylore/docs/cli.md)
+- [docs/observability.md](/home/simon/keylore/docs/observability.md)
+- [docs/operations.md](/home/simon/keylore/docs/operations.md)
+- [docs/threat-model.md](/home/simon/keylore/docs/threat-model.md)
+- [docs/keylore-spec-map.md](/home/simon/keylore/docs/keylore-spec-map.md)
+- [docs/roadmap.md](/home/simon/keylore/docs/roadmap.md)
+- [SECURITY.md](/home/simon/keylore/SECURITY.md)
+
+## Development
+
+```bash
+npm run typecheck
+npm test
+npm run build
+```
+
+## License
+
+Licensed under Apache-2.0. See [LICENSE](/home/simon/keylore/LICENSE) and [NOTICE](/home/simon/keylore/NOTICE).

package/bin/keylore-http.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+process.argv.push("--transport", "http");
+await import("../dist/index.js");

package/bin/keylore-stdio.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+process.argv.push("--transport", "stdio");
+await import("../dist/index.js");