hubkit-cli 0.1.0__tar.gz

hubkit_cli-0.1.0/.gitignore

@@ -0,0 +1,6 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage*

hubkit_cli-0.1.0/CHANGELOG.md

@@ -0,0 +1,36 @@
+# Changelog
+
+All notable changes to this project are recorded here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## [Unreleased]
+
+### Added
+- Install like miseenplace: `uv tool install hubkit-cli` (wheel built and installed in a scratch venv; not published), `hubkit skills --install DIR` (hub, hub-mep, hubkit-setup), `hubkit hooks [--skills-dir DIR] [--merge-guard]` prints the settings.json hooks block, and a `hubkit-setup` skill.
+- macOS and Windows support through one platform module (`hubcore/compat.py`); only Linux has been run so far.
+- Blockers (`order block|result`), watcher fixes, peer-report closing, `asks ls`, and warn-only merge guard.
+- Apache-2.0 license, `README.md` rewrite, `docs/` (architecture, configuration, commands, troubleshooting), `CONTRIBUTING.md`, `SECURITY.md`.
+- `pyproject.toml` with package metadata and ruff, mypy and pytest settings.
+- Tests for `learn.py promote-candidates`, `review` and the `address` error path, the entry-point import-failure path, and `doctor --check-clean`.
+
+### Fixed
+- Stop gate and review close: on a PR written by `user.github_login`, a COMMENT review at the head counts (verdict check, item close, queue advance). Other authors' PRs keep the non-author rule.
+- A brief is a review ask only when its first action on the PR is a review; "fix the findings in his review of #N" is not. A head moved by an owner asked to fix the PR raises no re-check alert; a review item still does.
+- PR numbers in examples, quotes and code spans of a brief are not tracked. Acknowledgements that name a PR are not tracked.
+- "waiting on the verdict" and similar awaiting wording no longer trips the verdict check.
+- `order open` never fires from a question, urgent word or not; the prompt hook says so and shows `hubkit order open` for doing it by hand.
+- `order close` requires evidence for every PR named in the order and names the missing ones.
+- A completed agent's task notification closes its routed item. Work ids are never reused after archive (`work.seq`).
+- `doctor` flags a stale or missing `seen/cron` when the crontab runs hubkit (`watchdog.cron_stale_min`).
+
+### Changed
+- `mep: UNVERIFIED` now says that the optional `mep` CLI was not found and how to turn the check off (`[mep] enabled = false`).
+- `doctor --check-clean` no longer scans `.git/` and also scans `.yml` and `.yaml` files.
+- Docstrings and type annotations on public functions; `SKILL.md` and `skills/` reworded for clarity.
+- The learnings file preamble says promoted rules go to the overlay.
+
+### Removed
+- The unused `tools.mep_cursor` config key.
+
+## [0.1.0] - 2026-11-04
+
+Initial private version: order clock, routed-work tracking, watchdog, stop gate, status block, end-of-day review and the learn loop.

hubkit_cli-0.1.0/CLAUDE.md

@@ -0,0 +1,55 @@
+# CLAUDE.md
+
+Guidance for an agent changing hubkit. Read `README.md` for what it does and `SKILL.md` for the behaviour contract the hub follows.
+
+## Layout
+
+```
+SKILL.md                  behaviour contract for the hub session (keep under ~200 lines)
+README.md                 operator view          docs/  architecture, configuration, commands, troubleshooting
+LICENSE (Apache-2.0)      pyproject.toml  ruff, mypy, pytest settings
+config.example.toml       generic config template   intents.example.toml   generic intents
+references/               design notes
+scripts/hubkit            entry point (hooks never raise; an import failure is logged and exits 0)
+scripts/learn.py          learnings log CLI
+scripts/hubcore/
+  cli.py                  argparse verbs, doctor
+  config.py               defaults + config loading (DEFAULTS is the full key list)
+  hooks.py                the hook events, bind/unbind, is_hub
+  orders.py               order ledger, intake, evidence-checked close
+  routed.py               routed-work items: record/chase/ladder, gh reads, heard-from, close
+  gate.py                 Stop-gate reasons
+  slow.py                 job records, estimates, usual-time baseline, SLOW check, estimate vs actual
+  watcher.py              hub/peer/watch/cron checks, desktop notify, false-alarm excuses, blocked-on link
+  status.py               work items, tick/watch, status block, EOD
+  store.py                state dir, locked/atomic writes, row IO
+  redact.py               secret redaction (every write passes through it)
+  learnings.py            learnings log
+tests/conftest.py         `env` fixture: scratch state, fake sessions, `env.run`/`env.hook`
+tests/test_hubkit.py      all tests
+tests/run_reverts.py      revert proof
+```
+
+## Run
+
+```
+python3 -m pytest tests -q
+ruff check . && mypy scripts/hubcore scripts/learn.py scripts/hubkit
+python3 tests/run_reverts.py          # slow (minutes), prints one line per entry, exits 0 only if all are OK
+python3 scripts/hubkit doctor --check-clean
+```
+
+Use the scratch state the `env` fixture gives. For a manual run set `HUBKIT_STATE` and `HUBKIT_CONFIG` to a scratch directory; never point tests or experiments at the live state dir or the live bind.
+
+## Rules
+
+- Every behaviour gets a test and a `run_reverts.py` entry: `(name, file, old, new, test)`, where `old` occurs exactly once in `file`, `new` breaks the behaviour, and `test` fails with it. An entry whose pattern is gone or whose test is not collected is reported BROKEN; fix or delete it. Do not edit `scripts/` while a revert run is in progress (it copies them per entry).
+- A test must be able to fail. Only GitHub (`gh`) may be a local stand-in, and only because tests cannot reach it; say so in the test. Use real 40-hex shas for heads.
+- Hooks always exit 0 and print nothing outside the bound hub. Fail loud inside the logic, not silently in the hook.
+- Config keys have defaults in `config.py` `DEFAULTS`; add new keys there and in `config.example.toml`.
+- Python 3.14; `except A, B:` without parentheses is the required form. Type annotations on functions; stdlib only.
+- Keep `SKILL.md`, `README.md` and `docs/` true: when a behaviour or verb changes, change them in the same edit, and check every command and path you write against the code.
+
+## No personal data in this directory
+
+No person's name, host, company or product term in scripts, tests, skill text or docs. `hubkit doctor --check-clean` scans these files for the terms in `[private] terms` of your config and must report none. Personal rules, names, terms and evidence live in `~/.config/hubkit/` (`config.toml`, `intents.toml`, `overlay.md`, `research/`), never here. Tests use neutral names such as `peer-a`.

hubkit_cli-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# Contributing
+
+Thanks for looking. hubkit is small on purpose: standard library only, Python 3.14. Linux is tested; macOS and Windows code exists but is unproven (see the README).
+
+## Set up and run the checks
+
+```bash
+git clone https://github.com/ankitkpandey1/hubkit && cd hubkit
+pip install pytest ruff mypy coverage
+python3 -m pytest tests -q                       # about 2 minutes: real subprocesses
+ruff check .
+mypy scripts/hubcore scripts/learn.py scripts/hubkit
+python3 tests/run_reverts.py                     # slow; run it when you touch a guarded behaviour
+```
+
+Tests and experiments use scratch state: set `HUBKIT_STATE` and `HUBKIT_CONFIG` to a temporary directory, or use the `env` fixture. Never point them at a live state directory or a live bind.
+
+## Rules
+
+- Every behaviour gets a test, and a guard gets a `tests/run_reverts.py` entry `(name, file, old, new, test)`: `old` occurs exactly once in `file`, `new` breaks the behaviour, and `test` fails with it.
+- A test must be able to fail. Do not mock hubkit's own code. Only `gh` may be a local stand-in, because tests cannot reach GitHub; say so in the test. Use real 40-hex shas for heads.
+- Hooks always exit 0 and print nothing outside the bound hub.
+- A new config key needs a default in `scripts/hubcore/config.py` (`DEFAULTS`), an entry in `config.example.toml` and a row in `docs/configuration.md`.
+- Type annotations on functions, a docstring on public ones, standard library only. `except A, B:` without parentheses (PEP 758) is the required form.
+- Keep `SKILL.md`, `README.md` and `docs/` true: change them in the same edit as the behaviour, and check each command and path against the code.
+- No personal names, hosts, companies or product terms in any file. Personal rules and names belong in the user's own `~/.config/hubkit/`. Tests use neutral names such as `peer-a`.
+
+## Pull requests
+
+Keep a change to one concern. Say what you ran. Add a line to `CHANGELOG.md` under Unreleased. By contributing you agree that your contribution is licensed under the Apache License 2.0, the same as the project.

hubkit_cli-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

hubkit_cli-0.1.0/PKG-INFO

@@ -0,0 +1,195 @@
+Metadata-Version: 2.5
+Name: hubkit-cli
+Version: 0.1.0
+Summary: Session supervisor for Claude Code: hooks-based multi-agent orchestration with order clocks, routed-work tracking, a watchdog and a stop gate, standard library only.
+Project-URL: Repository, https://github.com/ankitkpandey1/hubkit
+Project-URL: Documentation, https://github.com/ankitkpandey1/hubkit/tree/main/docs
+Project-URL: Issues, https://github.com/ankitkpandey1/hubkit/issues
+Author: Ankit Kumar Pandey
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: adaptive,agent-coordination,agents,claude-code,hooks,multi-agent,orchestration,supervisor,watchdog
+Requires-Python: >=3.14
+Description-Content-Type: text/markdown
+
+# hubkit
+
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+![Python 3.14+](https://img.shields.io/badge/python-3.14%2B-blue.svg)
+![Dependencies: none](https://img.shields.io/badge/dependencies-none-brightgreen.svg)
+
+**hubkit is a session supervisor for Claude Code: a hooks-based kit for multi-agent orchestration that keeps the one session coordinating your other sessions and agents honest. It gives each order a clock, tracks work routed to peers, blocks a premature "done", and learns from your corrections.**
+
+hubkit adapts to you. When you correct the hub ("I told you to wait for the review"), a hook notices, the hub records the correction as a class of mistake, and a class that repeats is promoted to a written rule in your own overlay file. A rule only counts as fixed after a check that the rule really exists, and it stays on probation until it has held. The words that open an urgent order, the clocks, what "done" means and every other setting live in your config files, not in the code, so the kit bends to how you work. This is a log-and-verify loop around the hub model, not machine learning: hubkit detects, stores and checks; the hub session writes the entries and rules.
+
+## Why use a Claude Code session supervisor
+
+A coordinating Claude Code session routes work to peers and background agents, then forgets. After a context compaction it no longer knows which order was urgent, who was asked to review what, or whether "done" was ever proven. hubkit keeps that record outside the model's memory, gives every order a clock and an evidence check, watches routed work for silence, and blocks the hub from ending a turn while it owes something. Example session:
+
+```console
+$ hubkit order open --kind hotfix --quote "hotfix the billing bug now"
+O-261105-bd22 hotfix [open] open 0m, idle 0m, chases 0; done needs: pr_merged,prod_live
+$ hubkit order move O-261105-bd22 --note "PR merged"
+$ hubkit order close O-261105-bd22 --evidence pr_merged=https://github.com/acme/repo/pull/12
+error: close refused: missing evidence 'prod_live'
+$ hubkit order close O-261105-bd22 --evidence pr_merged=https://github.com/acme/repo/pull/12 \
+      --evidence prod_live=https://example.com/deploy-log
+O-261105-bd22 closed
+```
+
+In a live hub, the prompt hook opens that order itself from your sentence, and the hub only reports "done" after the close succeeds.
+
+## What hubkit does for multi-agent coordination
+
+- **Learns from corrections.** A prompt hook flags correction phrases and repeated instructions. `scripts/learn.py` records, promotes and verifies them. See [docs/architecture.md](docs/architecture.md#the-learn-loop).
+- **Order clock.** Orders open from your own prompts (never from peer or harness text), each with a first-action limit, a stall limit and a definition of done checked by evidence on close.
+- **Routed-work tracking.** A hook on `SendMessage` and `Agent` records what the hub asked of whom, one item per (owner, PR). It follows last heard-from, moved heads and GitHub reviews at the PR head.
+- **Watchdog and wake-up.** `hubkit tick` (cron) and `hubkit watch` (a background process) raise alerts with back-off; a watch exit wakes an idle hub.
+- **Stop gate.** The Stop hook refuses to let the turn end while the hub owes something (no watch running, a stalled item, an unbacked verdict, a question to you that blocks nothing).
+- **Status, end-of-day review.** A status block at session start and on each prompt, a daily archive, and `hubkit eod`.
+
+`SKILL.md` is the behaviour contract the hub session reads. This file is the operator view.
+
+## Requirements
+
+- Linux. hubkit has only been run on Linux; macOS and Windows code exists but has never been run (see [Platform support](#platform-support)).
+- Python 3.14 or newer (the code uses `except A, B:` without parentheses, PEP 758). Standard library only.
+- [Claude Code](https://code.claude.com), which provides the hooks and the skills directory.
+- Optional: `gh` (GitHub CLI) on `PATH` for PR checks; without it items show "PR unknown". Optional: [`mep`](https://pypi.org/project/miseenplace-cli/) for a personal task list in the status block; without it the block shows `mep: UNVERIFIED (mep CLI not found ...)`, and `[mep] enabled = false` silences that.
+
+## Paste this into your agent
+
+```text
+Install hubkit with `uv tool install hubkit-cli`, run `hubkit skills --install DIR` with the skills directory
+for your tool, then run the hubkit-setup skill and follow it. Ask me only for things you cannot find out yourself.
+```
+
+hubkit runs on Claude Code hooks, so the skills directory is Claude Code's: `~/.claude/skills` (user level) or `.claude/skills` (project level). The PyPI name `hubkit-cli` is free as of 2026-11-06 and is not published yet; until it is, install straight from GitHub with `uv tool install git+https://github.com/ankitkpandey1/hubkit` (or from a clone with `uv tool install ./hubkit`).
+
+`hubkit skills --install DIR` copies three skills into `DIR`: `hub` (the rules and the scripts the hooks run), `hub-mep` (optional) and `hubkit-setup` (finds your facts, writes the config, registers the hooks, binds, proves it with `hubkit doctor`). Run it again after an upgrade to refresh the copies. `hubkit hooks --skills-dir DIR` prints the hooks block for `~/.claude/settings.json`.
+
+### Install by hand
+
+```bash
+git clone https://github.com/ankitkpandey1/hubkit ~/.claude/skills/hub
+python3 --version                             # 3.14 or newer
+python3 ~/.claude/skills/hub/scripts/hubkit doctor
+```
+
+The directory name must be `hub`: Claude Code finds the skill there, and the hooks and the stop gate use that path. `doctor` prints the config and state paths, the bind and the hook heartbeats; on a fresh install it shows `config: ... (defaults)` and `bind: none or dead`, which is correct.
+
+## Claude Code hook setup
+
+Add the hooks to `~/.claude/settings.json` (merge with any existing `hooks` block). Each command is a shim that prints a visible line if the script is missing, then runs one hook event:
+
+```json
+{
+  "hooks": {
+    "SessionStart": [{"hooks": [{"type": "command", "command": "[ -f $HOME/.claude/skills/hub/scripts/hubkit ] || echo 'hubkit: script missing'; python3 $HOME/.claude/skills/hub/scripts/hubkit hook session"}]}],
+    "UserPromptSubmit": [{"hooks": [{"type": "command", "command": "python3 $HOME/.claude/skills/hub/scripts/hubkit hook prompt"}]}],
+    "PostToolUse": [
+      {"matcher": "AskUserQuestion", "hooks": [{"type": "command", "command": "python3 $HOME/.claude/skills/hub/scripts/hubkit hook answer"}]},
+      {"matcher": "SendMessage|Agent", "hooks": [{"type": "command", "timeout": 6, "command": "python3 $HOME/.claude/skills/hub/scripts/hubkit hook routed"}]}
+    ],
+    "Stop": [{"hooks": [{"type": "command", "command": "python3 $HOME/.claude/skills/hub/scripts/hubkit hook stop"}]}]
+  }
+}
+```
+
+Hooks do nothing, print nothing and exit 0 in every session that is not the bound hub. Then, in the session that is to be the hub (interactive sessions only):
+
+```bash
+python3 ~/.claude/skills/hub/scripts/hubkit bind      # --pid N to name the process
+python3 ~/.claude/skills/hub/scripts/hubkit doctor    # now shows "bind: live <name>"
+```
+
+`hubkit unbind` frees it. For the `hubkit` command used below, add an alias such as `alias hubkit='python3 ~/.claude/skills/hub/scripts/hubkit'`.
+
+## Quick start
+
+```bash
+hubkit order open --kind hotfix --quote "hotfix the billing bug now"   # or let the prompt hook do it
+hubkit order ls
+hubkit work add --kind active --title "triage the flaky test"
+hubkit status                                                          # the status block
+python3 ~/.claude/skills/hub/scripts/learn.py add --class ask-before-merge --gate G5 \
+    --quote "I told you to wait for the review" --situation "..." --wrong "..." --right "..." --evidence "..."
+```
+
+Optional cron line for the watchdog (a no-op unless a hub is bound or an order is open). hubkit needs Python 3.14; cron's `PATH` can put an older `python3` first (for example `/usr/local/bin`), which fails on the first import and, with output sent to `/dev/null`, leaves no trace except a stale `seen/cron`. Name the interpreter:
+
+```
+*/5 * * * * /usr/bin/python3 $HOME/.claude/skills/hub/scripts/hubkit tick --if-bound
+```
+
+## Configuration files
+
+Everything personal lives outside the checkout, in `~/.config/hubkit/`:
+
+| File | Purpose |
+|---|---|
+| `config.toml` | Settings. Template: [`config.example.toml`](config.example.toml). Override the path with `$HUBKIT_CONFIG`. No file means generic defaults. |
+| `intents.toml` | Words that open an order, clocks, what "done" needs. Template: [`intents.example.toml`](intents.example.toml). |
+| `overlay.md` | Your own rules (people, accounts, routing). The hub reads it with `SKILL.md`; promoted learnings are written here. |
+| `ext/*.py` | Optional extensions: extra status lines and watchdog checks. |
+| `~/.local/state/hubkit/` | State: orders, work items, alerts, archive, status. Override with `$HUBKIT_STATE`. Refused if inside a git repository. |
+
+Every key is documented in [docs/configuration.md](docs/configuration.md).
+
+## What hubkit enforces and what it only warns about
+
+| Behaviour | Strength |
+|---|---|
+| The Stop hook holds the turn while the hub owes something: no watch running, a stalled item, an unbacked verdict, an unsolved blocker, an item over its estimate, a "done" while your newest prompt is unread | Enforced (blocks the turn end) |
+| An order closes only with the evidence its kind requires | Enforced (the close is refused) |
+| A learned class counts as fixed only if a rule for it exists | Enforced (the address is refused) |
+| A second job sent to a busy owner while an order is open; a brief that bans the action a blocker needs | Warning only |
+| `gh pr merge` with no live order naming that PR (the merge guard, `hubkit hook pretool`) | Warning only, never denies |
+| `hubkit doctor` warning when your `intents.toml` lacks keys the example has | Warning only |
+
+Details and exact rules: [SKILL.md](SKILL.md) and [docs/architecture.md](docs/architecture.md#stop-gate-gatepy).
+
+## Documentation
+
+- [docs/architecture.md](docs/architecture.md): hooks, orders, routed work, the stop gate and the learn loop, with a diagram.
+- [docs/configuration.md](docs/configuration.md): every `config.toml` and `intents.toml` key.
+- [docs/commands.md](docs/commands.md): every `hubkit` and `learn.py` verb.
+- [docs/troubleshooting.md](docs/troubleshooting.md): common problems and what to check.
+- [CONTRIBUTING.md](CONTRIBUTING.md), [SECURITY.md](SECURITY.md), [CHANGELOG.md](CHANGELOG.md).
+
+## Tests
+
+```bash
+python3 -m pytest tests -q          # real subprocesses, scratch state dirs only
+python3 tests/run_reverts.py        # each guard reverted in a copy must fail its test (minutes)
+```
+
+`run_reverts.py` exits 0 only when every reverted copy fails its test and every listed pattern and test exists. Install `pytest` first (`pip install pytest`).
+
+## Platform support
+
+All OS-specific code is in one module, `scripts/hubcore/compat.py` (standard library only): process start time and parent (`/proc` on Linux, `ps` on macOS, kernel32 through `ctypes` on Windows), file locks (`flock`, or `msvcrt` on Windows), the scheduler check (`crontab -l`, or `schtasks /query` on Windows) and UTF-8 stdio.
+
+| OS | Status |
+|---|---|
+| Linux | Full test suite run and passing here (ruff, mypy, pytest). |
+| macOS | The `ps` code path is exercised on Linux against the real `ps` (`tests/test_compat.py`), and mypy checks it with `--platform darwin`. Never run on a Mac. Not claimed to work until someone runs it there. |
+| Windows | The `ctypes` and `msvcrt` code is type-checked with `--platform win32` only. Never run on Windows. Tests that need a POSIX `sh` shim for `gh`, `crontab` or a notifier are skipped there. Not claimed to work until someone runs it there. There is no default desktop notification on Windows: set `tools.notify_cmd`. |
+
+There is no CI. Update this table only from a real run on that OS. On Windows the schedule is a Task Scheduler task whose name or command holds `hubkit` (for example `schtasks /create /sc minute /mo 5 /tn hubkit-tick /tr "python %USERPROFILE%\.claude\skills\hub\scripts\hubkit tick --if-bound"`), and hooks in `settings.json` call `python ...\hubkit hook <event>`.
+
+## Limits and known gaps
+
+- Python 3.14 only. macOS and Windows are written but unproven; see Platform support.
+- It targets one hub per machine. A second live hub is refused at bind.
+- Order creation takes a blocking `flock` (`scripts/hubcore/orders.py`); a process that holds the lock forever stalls order opens.
+- A hook payload with no `origin` field is treated as human input.
+- Redaction matches secret shapes and `key=value` forms. Natural-language secrets ("the password is hunter2") are not caught. See [SECURITY.md](SECURITY.md).
+- Whether a message to a peer is an ask, a reply or a follow-up is decided by rules in `scripts/hubcore/routed.py`; an unusual message can be misjudged.
+- The learn loop needs the hub model to act on the `CORRECTION` line; hubkit cannot make it record or write a rule, only refuse to mark a class fixed without one.
+- `skills/hub-mep` describes an optional integration with the `mep` task-list CLI and is of no use without it.
+- Hooks are written against the Claude Code hook payloads of late 2026; `payload-samples/` in the state dir records the real payload keys so a schema change is visible.
+
+## License
+
+Apache License 2.0. See [LICENSE](LICENSE). Copyright 2026 the hubkit contributors.