qriton 0.3.0 → 0.3.2

package/docs/energy.md

@@ -27,7 +27,7 @@ Set the interpreter in the workspace's `.qriton/config.json`. Merge this into ex
 
 `enabled` advertises the three agent tools. Direct CLI and slash commands remain available when it is false. Python packages are optional; normal coding sessions do not import Python, download checkpoints, or add Energy tool schemas by default.
 
-Review the project configuration with `qriton trust show`, then grant the reviewed fingerprint with `qriton trust grant <fingerprint>`. Project settings are applied only with a current grant; changes require review again. See [workspace configuration trust](workspace-trust.md).
+Review the project configuration with `qriton trust show`, then grant the reviewed fingerprint with `qriton trust grant <fingerprint>`. Project settings are applied only with a current grant; changes require review again. See [workspace configuration trust](https://unpkg.com/qriton/docs/workspace-trust.md).
 
 ```sh
 qriton energy doctor

package/docs/hlm.md

@@ -11,7 +11,7 @@ Qriton exposes the parts of the HLM ecosystem that fit a coding workspace: local
 | [HLM5 3B Base](https://huggingface.co/qriton/hlm5-3b-base) | Pinned sharded-safetensors import/download and FP32 completion | Inference only. Loader coverage does not establish full-model quality or editing support. |
 | [HLM5 certificate package](https://github.com/qriton/hlm5) | Upstream certificate/dose and editable-memory APIs | Separately installed; model weights remain frozen. |
 | `.hlm` programs | Text-addressed `memorize`, `correct`, `forget` through `/hlm`; numerical basin edits through `/energy` | Two explicitly separate adapters. |
-| [Energy Language](https://github.com/qriton/energy-lang) / `qriton-hlm` | Existing [HLM3 checkpoint workbench](energy.md) | Degree-3 polynomial Hopfield checkpoints; sampled structural checks and optional text evaluation. |
+| [Energy Language](https://github.com/qriton/energy-lang) / `qriton-hlm` | Existing [HLM3 checkpoint workbench](https://unpkg.com/qriton/docs/energy.md) | Degree-3 polynomial Hopfield checkpoints; sampled structural checks and optional text evaluation. |
 | `@qriton/hopfield-anomaly` | Existing memory recall plus `memory probe` diagnostics | Embedding novelty/composition and plain-vs-Hopfield retrieval comparison. |
 | Qriton's gesture, activity, audio, CIFAR-10 and ModelNet10 models | Discoverable in `hlm catalog` with their task and compatibility status | Their sensor/image inputs do not fit the coding/text workflow. No automatic download or unsupported inference claims. |
 | [HF certificate explorer](https://huggingface.co/spaces/qriton/hlm5-energy-language) | Reference demonstration | The local integration runs in its own Python process; private prompts are not sent to the Space. |
@@ -76,7 +76,7 @@ python3.10 -m venv .qriton/hlm-venv
 
 The interpreter needs `torch`, `tokenizers`, and, for 3B, `safetensors`. `sourcePath` contains the upstream `hlm5/` package. It can be empty if that package is already installed in the interpreter. Model code is executable code selected through this configuration; the downloader fetches model data, tokenizer, documentation and license files, not Python source.
 
-When using `.qriton/config.json`, review it with `qriton trust show` and grant its fingerprint with `qriton trust grant <fingerprint>` before running the commands below. Editing that file requires a new grant. See [workspace configuration trust](workspace-trust.md).
+When using `.qriton/config.json`, review it with `qriton trust show` and grant its fingerprint with `qriton trust grant <fingerprint>` before running the commands below. Editing that file requires a new grant. See [workspace configuration trust](https://unpkg.com/qriton/docs/workspace-trust.md).
 
 ```sh
 qriton hlm doctor

package/docs/network-policy.md

@@ -71,6 +71,6 @@ Remote service endpoints now require HTTPS. HTTP remains supported for loopback
 - Policy errors propagate to the UI and headless stderr. Cancellation remains active during response streaming. Connections are closed after requests and destroyed when the CLI session ends. Explicit per-request dispatchers do not use ambient proxy dispatchers; proxy-based deployment is not a supported policy profile yet.
 - `local-only` and `allowlist` block unconfined shell commands, Git commands, HLM/Energy Python execution, Ollama auto-start, model pulls, and recognized cloud-model delegation. Approval and `--yolo` do not bypass these checks. Local file tools and stored-session operations remain available.
 
-The [container profile](production-operations.md) permits shell, Git and Python in restricted modes with no container network and one workspace mount. Host processes, delegated downloads and service auto-start remain blocked. This does not sandbox other software, allowed services or trusted launcher/credential-store helpers. Untrusted Node preload code, replacement executables or a modified CLI can bypass application controls; protecting the launcher and installation is an operator responsibility. In-flight requests are not retroactively revoked when a policy file changes; subsequent requests fail and require restart. Memory scope enforcement and durable agent-tool records are described in the same operator guide.
+The [container profile](https://unpkg.com/qriton/docs/production-operations.md) permits shell, Git and Python in restricted modes with no container network and one workspace mount. Host processes, delegated downloads and service auto-start remain blocked. This does not sandbox other software, allowed services or trusted launcher/credential-store helpers. Untrusted Node preload code, replacement executables or a modified CLI can bypass application controls; protecting the launcher and installation is an operator responsibility. In-flight requests are not retroactively revoked when a policy file changes; subsequent requests fail and require restart. Memory scope enforcement and durable agent-tool records are described in the same operator guide.
 
 The HTTP client uses pinned `undici`. Its [Agent connection options](https://github.com/nodejs/undici/blob/v7.29.1/docs/docs/api/Client.md) provide the DNS lookup hook needed to validate and connect to the same addresses while retaining Node's streaming fetch and TLS handling. This avoids implementing a second HTTP/TLS stack. Programmatic integrations must use `withNetworkPolicy`; the CLI also binds the policy for terminal callbacks created outside the async session.

package/docs/shield.md

@@ -59,4 +59,4 @@ This layer does not sandbox processes, enforce organization memory scopes, repla
 
 The upstream HLM hook is not used: its published implementation initiates background classification and may return before a fresh result exists. Connecting HLM security classification would need a bounded, awaited decision through Qriton's HTTP boundary and separate accuracy/false-positive evidence.
 
-The Apache license and upstream notice are included in [THIRD_PARTY_NOTICES.md](../THIRD_PARTY_NOTICES.md).
+The Apache license and upstream notice are included in [THIRD_PARTY_NOTICES.md](https://unpkg.com/qriton/THIRD_PARTY_NOTICES.md).

package/docs/workspace-trust.md

@@ -57,7 +57,7 @@ QRITON_POLICY=/absolute/path/to/managed-policy.json qriton -C /path/to/project
 
 `allowProjectConfig: false` prevents project settings from being applied even if a receipt already exists, and prevents new grants. Project configuration is still read for inspection and validated as a bounded JSON object; malformed files cause an error. This switch does not disable reading repository instruction files as task context.
 
-The optional `network` block adds [destination limits and hosted-fallback controls](network-policy.md). Every applicable user and managed network policy must permit a request; project configuration cannot set network policy. Only the documented policy fields and `version` are accepted. Invalid, missing, or unreadable selected policy files fail closed. Changing or removing a loaded policy causes subsequent guarded actions to stop until Qriton is restarted. Keep the policy file, launcher environment, and user-state location under the administrator's control when using these limits for a managed deployment.
+The optional `network` block adds [destination limits and hosted-fallback controls](https://unpkg.com/qriton/docs/network-policy.md). Every applicable user and managed network policy must permit a request; project configuration cannot set network policy. Only the documented policy fields and `version` are accepted. Invalid, missing, or unreadable selected policy files fail closed. Changing or removing a loaded policy causes subsequent guarded actions to stop until Qriton is restarted. Keep the policy file, launcher environment, and user-state location under the administrator's control when using these limits for a managed deployment.
 
 ## Scope of these controls
 
@@ -65,4 +65,4 @@ This feature authorizes configuration. It does not approve every repository file
 
 CLI startup, interactive commands, agent mode changes, tool execution after approval, and background model/memory work check the loaded trust and policy. Internal programmatic callers that construct a `Config` directly are trusted host code; the public CLI uses the guarded loader.
 
-The implemented managed limits cover approval modes, project-configuration loading, and [HTTP destination policy](network-policy.md). [Session conflicts and save failures](session-recovery.md) also have recovery handling. This grant does not provide OS isolation or organization-wide memory administration. Restricted network profiles block unconfined shell, Git and Python execution. In unrestricted mode, shell commands run with the user's OS privileges. Application checks do not contain arbitrary code that already has access to the same account.
+The implemented managed limits cover approval modes, project-configuration loading, and [HTTP destination policy](https://unpkg.com/qriton/docs/network-policy.md). [Session conflicts and save failures](https://unpkg.com/qriton/docs/session-recovery.md) also have recovery handling. This grant does not provide OS isolation or organization-wide memory administration. Restricted network profiles block unconfined shell, Git and Python execution. In unrestricted mode, shell commands run with the user's OS privileges. Application checks do not contain arbitrary code that already has access to the same account.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "qriton",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Qriton CLI is a terminal coding agent that runs on infrastructure you control. Local models or any major model API, with a memory record, HLM, and Energy Language.",
   "type": "module",
   "bin": {
@@ -73,13 +73,6 @@
   ],
   "license": "MIT",
   "homepage": "https://qriton.com",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/qriton/qriton.git"
-  },
-  "bugs": {
-    "url": "https://github.com/qriton/qriton/issues"
-  },
   "author": "Marius Dima",
   "publishConfig": {
     "access": "public"

package/release/contract.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.3.0",
+  "version": "0.3.2",
   "supportedCodingModel": "local Ollama, plus xAI, Anthropic, OpenAI, and OpenAI-compatible APIs",
   "codingEvidence": "One session keeps its transcript, tools, and memory graph across those providers. HLM and Energy Language are separate local workbenches.",
   "localModels": "Optional. A bare qriton command still starts the configured local model. Local models are not the supported coding path.",