agentsquire 0.2.2__tar.gz → 0.4.0__tar.gz

{agentsquire-0.2.2 → agentsquire-0.4.0}/.gitignore

@@ -10,3 +10,7 @@ checkouts/
 # Local scratch / dev notes (never committed, never published)
 bugs.md
 feedback.md
+
+# specflo local state: the active-project pointer is per-clone session state,
+# not shared config. The durable record lives under docs/projects/.
+.specflo/

{agentsquire-0.2.2 → agentsquire-0.4.0}/CHANGELOG.md

@@ -8,6 +8,87 @@ The version is declared in two places that are kept in sync by the release
 tooling: `__version__` in `src/agentsquire/__init__.py` and `version` in
 `pyproject.toml`.
 
+## [0.4.0]
+
+### Added
+- **Interactive `skills uninstall`.** On an interactive terminal, a bare
+  `<consumer> skills uninstall` lists exactly the installed-and-ours skills -
+  enumerated from on-disk provenance stamps across every detected harness and
+  scope, so unstamped and foreign-stamped directories are never offered - then
+  removes the subset you pick after a destructive confirm summary. It re-checks
+  each stamp immediately before deleting, and is gated by the same TTY/CI/
+  explicit-flag rules as install. `-y/--yes` pre-answers the destructive
+  confirm (the picker still runs); `--no-input` skips the prompt entirely and
+  removes over the flag-selected `--harness NAME[:scope]` targets (default: all
+  detected at `--scope`, today's non-interactive meaning).
+- **Interactive `skills install`.** On an interactive terminal, a bare
+  `<consumer> skills install` now prompts: a checkbox of the detected
+  harnesses, then a per-harness scope select (a harness with only one scope,
+  e.g. hermes, is never offered an impossible choice), then a confirm summary
+  listing every `(harness, scope)` pair before anything is written. It ships
+  inside the mountable `skills_command_group`, so every consumer gets it with
+  no extra code. The prompt is launched only when stdin is an interactive TTY,
+  `CI` is unset, and none of `--harness`, `--scope`, `-y/--yes`, or
+  `--no-input` was passed - agents and scripts always run non-interactively.
+  New `--no-input` (force non-interactive) and `-y/--yes` (assume yes) flags.
+  Cancelling any prompt aborts with a notice and no writes; selecting nothing
+  or declining the confirm is a clean no-op; and because the confirm is the
+  single last gate, aborting a multi-harness plan writes none of it (never a
+  partial subset). Zero detected harnesses is the same clean error as the
+  non-interactive path, with no empty checkbox shown.
+- **`--harness` is now repeatable with an optional `:scope` suffix across all
+  four verbs (install, status, update, uninstall).** `install --harness
+  claude-code:project --harness pi` operates on that subset, each at its own
+  scope (a bare `NAME` uses the top-level `--scope`); omitting `--harness` still
+  targets every detected harness at `--scope`, and a single `--harness NAME`
+  behaves exactly as before. An unknown harness, a supported-but-undetected
+  harness, an invalid `:scope` value, or a `NAME:scope` the harness cannot
+  satisfy (e.g. `hermes:project`) each fail with a named error and write
+  nothing - a multi-target plan never partially installs.
+- **`questionary` is now a hard runtime dependency.** It backs the interactive
+  skill installer; a base install pulls it in with no extras, so the
+  interactive path always imports with no optional-import branching. It is
+  imported only in the interactive front-end module, so a non-interactive or
+  CI invocation never loads a terminal-UI library.
+
+### Changed
+- **install now resolves to an explicit `(harness, scope)` plan run by one
+  shared executor.** Internal refactor with no change to non-interactive
+  behavior; it is the seam the interactive front-end will hand its plan to.
+
+## [0.3.0]
+
+### Added
+- **agentsquire now ships its own runnable CLI, `squire` (long alias
+  `agentsquire`).** It dogfoods the library's consumer contract end to end,
+  carrying one bundled skill, mounting the ready-made skills group, emitting the
+  proactive staleness notice, and serving its own reference docs.
+  - `squire skills install|status|update|uninstall` - the standard group,
+    mounted the production way at user scope by default, operating on
+    agentsquire's one bundled skill.
+  - `squire guide [TOPIC]` - with no argument lists the reference topics (api,
+    harnesses, integration); with a topic, pages that canonical doc as raw
+    markdown. An unknown topic is a clean, non-zero error naming the valid
+    topics.
+  - `squire --version` prints the installed agentsquire version; `squire --help`
+    and `agentsquire --help` are identical below the usage line.
+  - A proactive staleness notice on stderr points at `squire skills update` when
+    an installed copy is out of date; suppressed under CI or
+    `AGENTSQUIRE_NO_UPDATE_CHECK`, and it never changes stdout or the exit code.
+- **`developing-with-agentsquire` bundled skill.** agentsquire carries one Agent
+  Skill as package data and marks itself skill-carrying under the
+  `agentsquire.skills` entry-point group - the same contract it documents for
+  consumers.
+- **The three reference docs are force-included into the wheel.** `docs/api.md`,
+  `docs/harnesses.md`, and `README.md` are packaged under `agentsquire/_docs/`
+  (as `api.md`, `harnesses.md`, `integration.md`) so `guide` has one
+  authoritative source that works from an installed wheel, with no committed
+  in-package duplicate.
+- **README Installation section.** Documents `pip install agentsquire`,
+  installing from a source clone, and - for developers building on agentsquire -
+  how to install the bundled `developing-with-agentsquire` skill and reference
+  docs into their own harness (`squire skills install`, `squire guide`).
+
 ## [0.2.2]
 
 ### Changed

{agentsquire-0.2.2 → agentsquire-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentsquire
-Version: 0.2.2
+Version: 0.4.0
 Summary: Let a Python package carry its own agent integrations and install them into whatever agent harness is present.
 Author: TacoTakumi
 License-Expression: MIT
@@ -20,6 +20,7 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Requires-Dist: click
 Requires-Dist: pyyaml
+Requires-Dist: questionary
 Description-Content-Type: text/markdown
 
 # AgentSquire
@@ -42,6 +43,42 @@ is by marker directory; every operation is local (no network in any verb). Each
 harness's directories, scopes, and behaviour are recorded in
 [docs/harnesses.md](docs/harnesses.md).
 
+## Installation
+
+    pip install agentsquire
+
+This installs the library and its own CLI, `squire` (aliased `agentsquire`). As
+a consumer you normally add `agentsquire` to your package's dependencies rather
+than having users install it directly - it rides in your wheel, and your users
+only ever see your tool.
+
+agentsquire dogfoods its own contract: it carries the
+`developing-with-agentsquire` skill and its reference docs as package data. When
+you build an app on agentsquire, install that skill into your own agent harness
+so the harness has the integration know-how on hand while it works:
+
+    squire skills install
+
+That copies `developing-with-agentsquire` (how to ship skills, mount the group,
+and wire the staleness hook) into every detected harness. The same reference
+docs are served at the terminal from the installed wheel - no checkout needed:
+
+    squire guide              # topics: api, harnesses, integration
+    squire guide api          # the Python API reference
+    squire guide integration  # this consumer integration guide
+
+### From source
+
+Clone the repository and install it into your environment:
+
+    git clone https://github.com/TacoTakumi/AgentSquire.git
+    cd AgentSquire
+    pip install .
+
+Add `-e` (`pip install -e .`) for an editable install if you plan to work on
+agentsquire itself. The repo uses [uv](https://docs.astral.sh/uv/): `uv sync`
+provisions a dev environment and `uv run pytest` runs the test suite.
+
 ## Consumer integration guide
 
 ### 1. Ship skills as package data

{agentsquire-0.2.2 → agentsquire-0.4.0}/README.md

@@ -18,6 +18,42 @@ is by marker directory; every operation is local (no network in any verb). Each
 harness's directories, scopes, and behaviour are recorded in
 [docs/harnesses.md](docs/harnesses.md).
 
+## Installation
+
+    pip install agentsquire
+
+This installs the library and its own CLI, `squire` (aliased `agentsquire`). As
+a consumer you normally add `agentsquire` to your package's dependencies rather
+than having users install it directly - it rides in your wheel, and your users
+only ever see your tool.
+
+agentsquire dogfoods its own contract: it carries the
+`developing-with-agentsquire` skill and its reference docs as package data. When
+you build an app on agentsquire, install that skill into your own agent harness
+so the harness has the integration know-how on hand while it works:
+
+    squire skills install
+
+That copies `developing-with-agentsquire` (how to ship skills, mount the group,
+and wire the staleness hook) into every detected harness. The same reference
+docs are served at the terminal from the installed wheel - no checkout needed:
+
+    squire guide              # topics: api, harnesses, integration
+    squire guide api          # the Python API reference
+    squire guide integration  # this consumer integration guide
+
+### From source
+
+Clone the repository and install it into your environment:
+
+    git clone https://github.com/TacoTakumi/AgentSquire.git
+    cd AgentSquire
+    pip install .
+
+Add `-e` (`pip install -e .`) for an editable install if you plan to work on
+agentsquire itself. The repo uses [uv](https://docs.astral.sh/uv/): `uv sync`
+provisions a dev environment and `uv run pytest` runs the test suite.
+
 ## Consumer integration guide
 
 ### 1. Ship skills as package data

{agentsquire-0.2.2 → agentsquire-0.4.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "agentsquire"
-version = "0.2.2"
+version = "0.4.0"
 description = "Let a Python package carry its own agent integrations and install them into whatever agent harness is present."
 readme = "README.md"
 license = "MIT"
@@ -28,8 +28,19 @@ classifiers = [
 dependencies = [
     "pyyaml",
     "click",
+    "questionary",
 ]
 
+[project.scripts]
+squire = "agentsquire.console:main"
+agentsquire = "agentsquire.console:main"
+
+# agentsquire dogfoods its own consumer contract: it carries one bundled skill
+# (developing-with-agentsquire) and marks itself skill-carrying under the same
+# entry-point group it tells consumers to use. Nothing reads this at launch.
+[project.entry-points."agentsquire.skills"]
+agentsquire = "agentsquire"
+
 [dependency-groups]
 dev = [
     "build",
@@ -53,6 +64,15 @@ include = [
     "/docs/harnesses.md",
 ]
 
+# Force-include the three canonical docs into the wheel so `guide` has a single
+# authoritative source with no hand-maintained in-package duplicate. The sources
+# live only under docs/ and README.md; nothing is committed under the package.
+# README.md becomes the `integration` topic.
+[tool.hatch.build.targets.wheel.force-include]
+"docs/api.md" = "agentsquire/_docs/api.md"
+"docs/harnesses.md" = "agentsquire/_docs/harnesses.md"
+"README.md" = "agentsquire/_docs/integration.md"
+
 [tool.pytest.ini_options]
 testpaths = ["tests"]
 pythonpath = ["src"]

{agentsquire-0.2.2 → agentsquire-0.4.0}/src/agentsquire/__init__.py

@@ -6,7 +6,7 @@ enumerate skills from a source, detect harnesses, then install / status /
 update / uninstall. See docs/api.md for the reference.
 """
 
-__version__ = "0.2.2"
+__version__ = "0.4.0"
 
 from agentsquire.harnesses import (
     CLAUDE_CODE,