@etiquekit/etq 1.0.5 → 1.0.7

package/AGENTS.md

@@ -1,28 +1,37 @@
 # Etiquette Agent Guide
 
-This repo is the Etiquette source repo. Keep the all-developer onboarding path small.
+## If you installed this package
 
-## Default Rule
+You are reading the INSTALLED copy of the Etiquette CLI (npm or tarball) —
+"this repo" below refers to Etiquette's source repository, not your project.
+As an agent working in a project governed by Etiquette:
 
-New engineers should start with:
+1. Read [README.md](README.md), then [QuickStart.md](QuickStart.md).
+2. Orient with `etq whereami`; join your assigned seat; read the task
+   envelope and the project's `docs/work/runbooks/WORKING_DISCIPLINE.md`.
+3. Respect allowed writes, run the named validation, write the receipt at
+   the path `pickup` names, post it, and pass `etq return check` before
+   claiming completion.
 
-1. [README.md](README.md)
-2. [docs/SEAT_PROVISIONING.md](docs/SEAT_PROVISIONING.md)
-3. [templates/etiquette-vanilla-v0/README.md](templates/etiquette-vanilla-v0/README.md)
-
-Do not send new seats through internal history, old coordination lanes, or maintainer-only notes.
+Commands record evidence; they never grant, merge, close, publish, or
+promote.
 
-## Ownership
+## If you are working on the Etiquette source repo
 
-This repo owns:
+Keep the all-developer onboarding path small. New engineers start with:
 
-- the minimal vanilla seat scaffold;
-- optional runtime seat-pack scaffolds;
-- shared task, readiness, and receipt contracts;
-- validation scripts for release hygiene.
+1. [README.md](README.md)
+2. [docs/SEAT_PROVISIONING.md](docs/SEAT_PROVISIONING.md)
+3. [templates/etiquette-vanilla-v0/README.md](templates/etiquette-vanilla-v0/README.md)
 
-This repo does not own product repos, product lane state, secrets, hosted services, or runtime vendor setup.
+Do not send new seats through internal history, old coordination lanes, or
+maintainer-only notes.
 
-## Editing Rule
+This repo owns: the minimal vanilla seat scaffold; optional runtime seat-pack
+scaffolds; shared task, readiness, and receipt contracts; validation scripts
+for release hygiene. It does not own product repos, product lane state,
+secrets, hosted services, or runtime vendor setup.
 
-Release-facing docs must stay role-based and portable. Do not introduce person names, local machine paths, historical bus references, or project-specific lane IDs into the default onboarding surface.
+Release-facing docs must stay role-based and portable. Do not introduce
+person names, local machine paths, historical bus references, or
+project-specific lane IDs into the default onboarding surface.

package/QuickStart.md

@@ -29,12 +29,16 @@ export PATH="$HOME/.etiquette/bin:$PATH"
 
 From the project repo:
 
+Same core order as the README quickstart; `handoff`/`whereami` are optional
+orientation verbs. `bootstrap local` does not replace `init`.
+
 ```sh
+etq init --project "$PWD"
+etq doctor --project "$PWD"
+etq bootstrap local --project "$PWD" --profile codex-cc-gemini --task-prefix APP
 etq setup --target auto --project "$PWD"
 etq handoff --project "$PWD" --profile codex-cc-gemini --task-prefix APP
-etq bootstrap local --project "$PWD" --profile codex-cc-gemini --task-prefix APP
 etq whereami --project "$PWD" --seat codex-seat --task APP-001
-etq doctor --project "$PWD"
 etq join --project "$PWD" --seat codex-seat
 etq pickup --project "$PWD" --seat codex-seat --task APP-001 --allow-current-project --text
 etq console board --project "$PWD" --text
@@ -60,7 +64,11 @@ envelope, and runbook. For branch hygiene, read [docs/WORKTREE_QOL.md](docs/WORK
 
 ## 4. Check And Record Evidence
 
-Create checkable dispatch examples, then run the generated command:
+Completion gate: write the receipt at the path `pickup` names, post it
+(`etq post --role implementation-return --lane <task> --from <seat> --to <seat>`),
+then `etq return check`. Separately, `dispatch check` gates ROUTING before
+work begins — create checkable dispatch examples, then run the generated
+command:
 
 ```sh
 etq dispatch scaffold --project "$PWD" --task-id APP-001 --seat codex-seat

package/README.md

@@ -20,7 +20,7 @@ curl -fsSL https://etiquekit.com/install.sh | sh   # or: native installer
 ```
 
 Requires `bun >= 1.3` and `git >= 2.40`. macOS and Linux. The installer
-verifies signatures against a pinned public key before anything executes.
+verifies signatures against a pinned key before executing.
 
 ## Sixty seconds to a governed workspace
 
@@ -30,21 +30,24 @@ etq doctor --project .                # readiness — green before work
 etq bootstrap local --project . \
     --profile codex-cc-gemini --task-prefix APP
 etq setup --target auto --project .   # register your agent CLI (explicit)
-etq join --seat dev-a --project .
+etq join --seat codex-seat --project . # profile seats: codex/cc/gemini/manager
 etq console board --project . --text  # the live task board
 ```
 
 Per-runtime seat packs: `provision-seat claude-code` · `provision-seat codex`
 · `provision-seat gemini` · `provision-seat ollama` · `provision-seat openrouter`.
 
-The daily loop is three verbs:
+The daily loop:
 
 ```sh
-etq pickup --seat dev-a --task APP-001 --expect-project-id <id> --text
-# ... do the work (you, or your agent) ...
-etq return check --task APP-001 --seat dev-a   # the evidence gate
+etq pickup --seat codex-seat --task APP-001 --expect-project-id <id> --text
+# ... do the work; write the receipt at the path pickup names ...
+etq post --role implementation-return --lane APP-001 \
+    --from codex-seat --to manager-seat --project .
+etq return check --task APP-001 --seat codex-seat   # the completion gate
 ```
 
+(`dispatch check` gates routing BEFORE work; `return check` gates completion.)
 Every step appends to the workspace journal — an append-only event log inside
 your repo. Nothing leaves your machine: no backend, no telemetry, no account.
 
@@ -58,15 +61,13 @@ your repo. Nothing leaves your machine: no backend, no telemetry, no account.
 | Receipt | What proves the work happened? |
 | Promotion gate | Where does candidate work become accepted truth? |
 
-Commands can initialize, check, record evidence, and project read models.
-They **do not** grant authority, merge, close work, publish, or promote truth.
-Execution returns evidence; it never mints authority.
+Commands initialize, check, record evidence, and project read models. They
+**never** grant, merge, close, publish, or promote — evidence, not authority.
 
 ## Verify releases
 
-The release signing public key has this SHA-256 fingerprint — cross-check it
-against the copy at https://etiquekit.com/docs/ before trusting a downloaded
-key:
+The signing key's SHA-256 fingerprint — cross-check against the copy at
+https://etiquekit.com/docs/ before trusting a downloaded key:
 
 ```
 917fbced1d6a82897ec3441a1d12947803ca4d42a6bc63d3412dee8bf8c3ce31
@@ -76,5 +77,4 @@ Then `openssl dgst -sha256 -verify <key> -signature SHA256SUMS.sig SHA256SUMS`
 and `shasum -a 256 -c SHA256SUMS`. If any step fails: stop, do not install.
 
 ## License
-
 Proprietary; distributed as compiled bundles for convenience.