agentbundle 0.4.0__tar.gz → 0.5.0__tar.gz

{agentbundle-0.4.0 → agentbundle-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentbundle
-Version: 0.4.0
+Version: 0.5.0
 Summary: npm for your coding agent. Install packs of skills, subagents, and hooks into any repo, for every major agent.
 Author-email: eugenelim <eugenelim@users.noreply.github.com>
 License: Apache-2.0 OR MIT
@@ -39,6 +39,12 @@ That lands `core`, the flagship pack and the loop itself, in your repo. Claude C
 # See what's in a catalogue
 agentbundle list-packs git+https://github.com/eugenelim/agent-ready-repo
 
+# See the catalogue's curated install profiles
+agentbundle list-profiles git+https://github.com/eugenelim/agent-ready-repo
+
+# Install a whole curated profile — a single-scope set of packs — in one command
+agentbundle install --profile inception git+https://github.com/eugenelim/agent-ready-repo
+
 # Install the flagship loop into this repo
 agentbundle install --pack core git+https://github.com/eugenelim/agent-ready-repo
 
@@ -52,7 +58,7 @@ agentbundle install --pack core git+https://github.com/eugenelim/agent-ready-rep
 agentbundle upgrade --pack core --to 0.4.0 git+https://github.com/eugenelim/agent-ready-repo
 ```
 
-A catalogue is a git URL or a local path. Installs auto-detect your agent; pass `--adapter` to override.
+A catalogue is a git URL or a local path. Installs auto-detect your agent; pass `--adapter` to override. A **profile** is a catalogue-curated, single-scope set of packs you install in one command — it declares its own scope, so `--scope` doesn't apply.
 
 ## Build your own catalogue
 

{agentbundle-0.4.0 → agentbundle-0.5.0}/README.md

@@ -21,6 +21,12 @@ That lands `core`, the flagship pack and the loop itself, in your repo. Claude C
 # See what's in a catalogue
 agentbundle list-packs git+https://github.com/eugenelim/agent-ready-repo
 
+# See the catalogue's curated install profiles
+agentbundle list-profiles git+https://github.com/eugenelim/agent-ready-repo
+
+# Install a whole curated profile — a single-scope set of packs — in one command
+agentbundle install --profile inception git+https://github.com/eugenelim/agent-ready-repo
+
 # Install the flagship loop into this repo
 agentbundle install --pack core git+https://github.com/eugenelim/agent-ready-repo
 
@@ -34,7 +40,7 @@ agentbundle install --pack core git+https://github.com/eugenelim/agent-ready-rep
 agentbundle upgrade --pack core --to 0.4.0 git+https://github.com/eugenelim/agent-ready-repo
 ```
 
-A catalogue is a git URL or a local path. Installs auto-detect your agent; pass `--adapter` to override.
+A catalogue is a git URL or a local path. Installs auto-detect your agent; pass `--adapter` to override. A **profile** is a catalogue-curated, single-scope set of packs you install in one command — it declares its own scope, so `--scope` doesn't apply.
 
 ## Build your own catalogue
 

agentbundle-0.5.0/agentbundle/_data/profile.schema.json

@@ -0,0 +1,21 @@
+{
+  "type": "object",
+  "required": ["scope", "description", "packs"],
+  "additionalProperties": false,
+  "properties": {
+    "scope": {"enum": ["repo", "user"]},
+    "description": {"type": "string"},
+    "packs": {
+      "type": "array",
+      "minItems": 1,
+      "items": {
+        "type": "object",
+        "required": ["pack"],
+        "additionalProperties": false,
+        "properties": {
+          "pack": {"type": "string"}
+        }
+      }
+    }
+  }
+}

{agentbundle-0.4.0 → agentbundle-0.5.0}/agentbundle/build/scope_rails.py

@@ -299,6 +299,16 @@ def run_all(
 # ---------------------------------------------------------------------------
 
 
+# Adapters whose hook-wiring projects via `merge-into-agent-json` (a
+# pack-owned `.kiro/agents/<attach-to-agent>.json`): the legacy `kiro`
+# block and the `kiro-cli` adapter. The `attach-to-agent` rails below
+# validate that merge target, so they fire for this family. `kiro-ide`
+# (and the `kiro` *install alias*, which routes to kiro-ide) DROPS
+# hook-wiring and is intentionally absent — there is no merge target to
+# validate. Mirrors install.py's merge dispatch.
+_MERGE_INTO_AGENT_JSON_ADAPTERS = frozenset({"kiro", "kiro-cli"})
+
+
 def check_kiro_attach_to_agent(
     pack_name: str,
     wiring_tomls: dict[str, dict],
@@ -325,7 +335,7 @@ def check_kiro_attach_to_agent(
       target_adapters: iterable of adapter names the pack is being
         validated against. No-op when ``kiro`` is absent.
     """
-    if "kiro" not in set(target_adapters or ()):
+    if not (set(target_adapters or ()) & _MERGE_INTO_AGENT_JSON_ADAPTERS):
         return None
     for wiring_name, body in wiring_tomls.items():
         attach = body.get("attach-to-agent") if isinstance(body, dict) else None
@@ -485,7 +495,7 @@ def check_kiro_wiring(
     would let a pack reach outside its source tree. A wiring TOML that
     fails to parse counts as a refusal on its own.
     """
-    if "kiro" not in set(target_adapters or ()):
+    if not (set(target_adapters or ()) & _MERGE_INTO_AGENT_JSON_ADAPTERS):
         return None
 
     loaded = _load_pack_hook_wiring_safely(pack_path, pack_name)

{agentbundle-0.4.0 → agentbundle-0.5.0}/agentbundle/cli.py

@@ -1,9 +1,11 @@
 """`agentbundle` CLI dispatcher — argparse over the eleven F-cli subcommands.
 
 Subcommand order on the parser matches the canonical install-workflow order
-from the spec (discovery-first): `list-packs`, `list-targets`, `scaffold`,
-`install`, `validate`, `render`, `adapt`, `diff`, `upgrade`, `uninstall`,
-`init-state`.
+from the spec (discovery-first): `list-packs`, `list-profiles`, `list-targets`,
+`scaffold`, `install`, `validate`, `render`, `adapt`, `diff`, `upgrade`,
+`uninstall`, `init-state`, `config`, `reconcile`. `list-profiles` (RFC-0034)
+lists the catalogue's curated single-scope install profiles; `install
+--profile <name>` installs one.
 
 Each subcommand's `run(args) -> int` lives under `agentbundle.commands.*`;
 this module wires `argparse` and prints `--version`. No business logic here.
@@ -192,6 +194,14 @@ def _build_parser() -> argparse.ArgumentParser:
     sp.add_argument("catalogue", help="Catalogue URI (local path or git+https://...).")
     sp.set_defaults(func=_lazy("list_packs"))
 
+    # --- list-profiles --- (catalogue query; profiles declare their own scope)
+    sp = subparsers.add_parser(
+        "list-profiles",
+        help="List curated install profiles available in a catalogue URI.",
+    )
+    sp.add_argument("catalogue", help="Catalogue URI (local path or git+https://...).")
+    sp.set_defaults(func=_lazy("list_profiles"))
+
     # --- list-targets --- (--scope as read-only filter)
     sp = subparsers.add_parser(
         "list-targets",
@@ -215,7 +225,23 @@ def _build_parser() -> argparse.ArgumentParser:
         "install",
         help="Install a pack from a catalogue URI into the adopter repo.",
     )
-    sp.add_argument("--pack", required=True)
+    # pack-profiles: `--pack` and `--profile` are a required mutually-exclusive
+    # group. `--pack` was a bare `required=True` arg; making it a member of a
+    # required mutex group keeps "exactly one of pack/profile" without losing
+    # the requiredness. `--scope` with `--profile` is rejected at the handler
+    # (a profile declares its own scope); argparse can't express that mutex
+    # because `--scope` is valid alongside `--pack`.
+    _pack_or_profile = sp.add_mutually_exclusive_group(required=True)
+    _pack_or_profile.add_argument("--pack")
+    _pack_or_profile.add_argument(
+        "--profile",
+        help=(
+            "Install a curated single-scope set of packs from "
+            "<catalogue>/profiles/<name>.toml in one command (RFC-0034). "
+            "Mutually exclusive with --pack; --scope is not allowed (the "
+            "profile declares its own scope)."
+        ),
+    )
     sp.add_argument("catalogue", help="Catalogue URI (local path or git+https://...).")
     sp.add_argument("--output", default=".")
     sp.add_argument("--scope", choices=("repo", "user"))