diff --git a/PRIVACY.md b/PRIVACY.md index dad690a..dadf845 100644 --- a/PRIVACY.md +++ b/PRIVACY.md @@ -15,7 +15,7 @@ and there is no tenth: "schema": 1, "exception": "ManifestError", "frames": [{"module": "hullwork.manifest", "function": "parse_manifest", "lineno": 707}], - "release": "0.1.0a8", + "release": "0.1.0a9", "python": "3.12.13", "platform": "linux", "operation": "receiver", diff --git a/README.md b/README.md index c06ff5d..669cfbf 100644 --- a/README.md +++ b/README.md @@ -152,7 +152,7 @@ code, and writes nothing outside a directory you name. → above, and [docs/install.md § 1](docs/install.md#1-try-the-agent-half) **2. The evaluation stack — recommended for a first look.** Needs Docker and nothing else, with **no -clone and no build**: one compose file and a published image (`ghcr.io/easybytehub/hullwork:0.1.0a8`, +clone and no build**: one compose file and a published image (`ghcr.io/easybytehub/hullwork:0.1.0a9`, amd64 and arm64). One container — the half that answers webhooks — which starts with no credentials at all and says in a sentence what it cannot do yet. → [docs/install.md § 2](docs/install.md#2-the-evaluation-stack) diff --git a/docker-compose.yml b/docker-compose.yml index 7600b91..8f9ac25 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -25,7 +25,7 @@ services: # # To run your own build instead — a change you are testing, or an architecture with no published # image — add `build: .` beside this line from a checkout, and `docker compose up -d --build`. - image: ghcr.io/easybytehub/hullwork:0.1.0a8 + image: ghcr.io/easybytehub/hullwork:0.1.0a9 ports: - "127.0.0.1:8000:8000" restart: unless-stopped diff --git a/docs/install.md b/docs/install.md index 324e32d..ee0a7e5 100644 --- a/docs/install.md +++ b/docs/install.md @@ -93,10 +93,10 @@ is the half that answers webhooks. Nothing here can push to anything. curl -O https://raw.githubusercontent.com/easybytehub/hullwork/main/docker-compose.yml docker compose up -d curl http://127.0.0.1:8000/health -# {"status":"ok","version":"0.1.0a8"} +# {"status":"ok","version":"0.1.0a9"} ``` -The image is `ghcr.io/easybytehub/hullwork:0.1.0a8`, built for amd64 and arm64, pinned in that compose +The image is `ghcr.io/easybytehub/hullwork:0.1.0a9`, built for amd64 and arm64, pinned in that compose file rather than floating on `latest`. From a clone, `docker compose up -d --build` builds your own instead — which is what you want if you are testing a change. @@ -122,15 +122,6 @@ Losing them would make every already-known error look new tomorrow morning. ### Asking it how it is -> **Built and unreleased**, as of 2026-08-10. Everything in this section is in no image you can pull: -> `docs/published-surface.json` records `0.1.0a8`, and these routes are items 203 to 208. Until a -> release carries them, the CLI below is the whole of it — and this note stays, because the rule is -> that documentation describes the released artefact rather than this checkout (`CONTRIBUTING.md`). -> -> Written down rather than deleted because the guard that catches this **cannot see it**: it compares -> documented *commands* against the published image and knows nothing about URLs, so a route -> documented before it exists passes every test. Recorded as work item 209. - **From the page, which is the point** (DR-0022). Set a password once — `docker compose exec api hullwork password`, read from a prompt so it is not in your shell history — and everything below is a URL: @@ -165,8 +156,8 @@ you wrote in a file. ### A page a teammate can read Two doors, and they are for two people -(DR-0021). **The first is unreleased**, per the note -above; the second has worked since `0.1.0a5`. +(DR-0021). The first arrived in `0.1.0a9`; the second +has worked since `0.1.0a5`. **Yours is `/page/me/`**, behind the password. Nothing to lose, nothing to copy, and it is the only one that administers anything. diff --git a/docs/published-surface.json b/docs/published-surface.json index 5d5f0b3..b6f3bd7 100644 --- a/docs/published-surface.json +++ b/docs/published-surface.json @@ -1,8 +1,8 @@ { "_": "Generated by scripts/record-the-published-surface.py from the image itself. Do not hand-edit: a documented capability that is not in here is one nobody can run, and editing this file would make that true silently.", - "image": "ghcr.io/easybytehub/hullwork:0.1.0a8", - "version": "0.1.0a8", - "recorded": "2026-08-09", + "image": "ghcr.io/easybytehub/hullwork:0.1.0a9", + "version": "0.1.0a9", + "recorded": "2026-08-11", "commands": { "hullwork": [ "--help", @@ -124,7 +124,8 @@ ], "hullwork init": [ "--help", - "--into" + "--into", + "--no-questions" ], "hullwork page-token": [ "--help",