sept-agent 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CONTRIBUTING.md
CHANGED
|
@@ -42,3 +42,7 @@ Only root, client and hands are public npm entries. Public API changes need stri
|
|
|
42
42
|
Compilation and isolated tests support delivery; the actual installed runtime path is the completion criterion. Exercise the changed installed CLI/public import through production Pi and supplied hands. Container input changes require a fresh no-cache image and affected installed proof. The npm tarball excludes the Docker build context; build from full source and inspect final package inventory, source maps, legal/provenance files and allowed imports.
|
|
43
43
|
|
|
44
44
|
Record exact source/tar/image/dependency identity, cwd/commands, actual child exit/signal/join, original failures and separately observed finalizers. Do not turn wrapper exit0 into a product verdict. Export needed tmpfs data before stopping the exact owned generation; independently close worker, provider/listener, attachments/leases and namespace even if one cleanup fails. Preserve stopped-generation proof, mutex inodes, evidence, recovery and unrelated resources. Never prune/delete them as incidental cleanup. See [operator finalization](docs/pi-contract.md#export-and-finalize-the-owned-generation).
|
|
45
|
+
|
|
46
|
+
## Automated package releases
|
|
47
|
+
|
|
48
|
+
[Release setup and retry policy](https://github.com/DB-Conneely/sept/blob/main/docs/releasing.md) describes the GitHub-hosted Linux/amd64 gate and main-push npm/GHCR/GitHub release workflow. It uses no live provider or local model. The publish job consumes the exact tested tarball and saved image; deployment remains manual.
|
package/README.md
CHANGED
|
@@ -6,7 +6,9 @@ SEPT is a durable, single-slot task worker for Node.js, built on the native Pi D
|
|
|
6
6
|
|
|
7
7
|
Requires Node.js **22.19.0 or newer**, ESM, Pi credentials or a suitable configured model, persistent local state, and an operator-supplied Docker Linux hands namespace. Valid hands are required even for text-only tasks. The package does not install Docker, serve models or provision hands.
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
After npm publication, add SEPT to your application with `npm install --save-exact sept-agent`. The command is `sept` and the import name is `sept-agent`.
|
|
10
|
+
|
|
11
|
+
To install a retained exact package artifact for a qualified source revision:
|
|
10
12
|
|
|
11
13
|
```sh
|
|
12
14
|
npm install --save-exact /absolute/path/sept-agent-0.1.0.tgz
|
|
@@ -88,3 +90,5 @@ The bearer comes from `SEPT_TOKEN`, never a CLI token option. Every HTTP route r
|
|
|
88
90
|
Support is scoped to qualified source/image/host combinations; see [version and support](docs/index.md#version-and-support). The npm artifact is a consumer package; build the Docker image from a pinned complete repository checkout. Host npm Pi stays stock; the [four native-search image assets](image/pi-native-search/README.md) describe the image-only overlay. No publication or deployment is performed by these instructions.
|
|
89
91
|
|
|
90
92
|
SEPT is [MIT licensed](LICENSE). [NOTICE](NOTICE) retains the known upstream attribution and image-overlay provenance.
|
|
93
|
+
|
|
94
|
+
Maintainers: [automatic checks and publishing setup](https://github.com/DB-Conneely/sept/blob/main/docs/releasing.md) describes main-push releases, npm trusted publishing and GHCR configuration. Publishing does not deploy a service.
|