agentbundle 0.41.1__tar.gz → 0.43.0__tar.gz

{agentbundle-0.41.1/agentbundle.egg-info → agentbundle-0.43.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentbundle
-Version: 0.41.1
+Version: 0.43.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-Expression: Apache-2.0 OR MIT
@@ -34,6 +34,31 @@ python -m pip install agentbundle
 
 Requires Python 3.11+. Runs on macOS, Linux, and Windows.
 
+## What's new in 0.43.0
+
+An installed direct skill can now move to a later repository revision with
+`agentbundle upgrade --skill <name>`. The command re-runs direct-source
+admission, shows the same capability consent surface as install, refuses a
+capability widening, previews writes and removals, and deletes files the new
+revision dropped before recording the updated row.
+
+Install identity now excludes the repository ref. An install at a different ref
+still exits 1, but its re-coded refusal names `upgrade --skill --source` instead
+of reporting a source collision; a moved `source-path` now refuses instead of
+silently self-healing; and a byte-identical reinstall still repairs the
+projection in place. Remove-then-install is the terminating remediation for the
+moved-`source-path` collision.
+
+## What's new in 0.42.0
+
+The portable Agent Plugin route now reaches every command that works with
+distribution routes. `validate` accepts a pack declaring the
+`per-pack-agent-plugin` recipe, `render --target agent-plugin` selects it,
+`install --emit-install-routes` also writes `agent-plugins/<pack>/`, and
+`install`, `diff`, and `upgrade` each recognise a portable install. Every
+surface now reads its route set from the route contract, so a route declared
+there reaches all of them at once. Published package bytes are unchanged.
+
 ## What's new in 0.41.1
 
 The same release as 0.41.0, which never reached PyPI: its release run failed a

{agentbundle-0.41.1 → agentbundle-0.43.0}/README-pypi.md

@@ -14,6 +14,31 @@ python -m pip install agentbundle
 
 Requires Python 3.11+. Runs on macOS, Linux, and Windows.
 
+## What's new in 0.43.0
+
+An installed direct skill can now move to a later repository revision with
+`agentbundle upgrade --skill <name>`. The command re-runs direct-source
+admission, shows the same capability consent surface as install, refuses a
+capability widening, previews writes and removals, and deletes files the new
+revision dropped before recording the updated row.
+
+Install identity now excludes the repository ref. An install at a different ref
+still exits 1, but its re-coded refusal names `upgrade --skill --source` instead
+of reporting a source collision; a moved `source-path` now refuses instead of
+silently self-healing; and a byte-identical reinstall still repairs the
+projection in place. Remove-then-install is the terminating remediation for the
+moved-`source-path` collision.
+
+## What's new in 0.42.0
+
+The portable Agent Plugin route now reaches every command that works with
+distribution routes. `validate` accepts a pack declaring the
+`per-pack-agent-plugin` recipe, `render --target agent-plugin` selects it,
+`install --emit-install-routes` also writes `agent-plugins/<pack>/`, and
+`install`, `diff`, and `upgrade` each recognise a portable install. Every
+surface now reads its route set from the route contract, so a route declared
+there reaches all of them at once. Published package bytes are unchanged.
+
 ## What's new in 0.41.1
 
 The same release as 0.41.0, which never reached PyPI: its release run failed a

{agentbundle-0.41.1 → agentbundle-0.43.0}/README.md

@@ -172,10 +172,10 @@ Developers installing from your fork get the internal channel without a manual
 A malformed `enabled = true` config fails closed — no silent fallback to the public
 source.
 
-See the full enterprise adoption guide at
-`docs/guides/_shared/how-to/use-an-artifactory-catalogue.md` for all six flows
-(org bootstrap, repo-scope CI upgrade, user-scope MDM, source-conflict remediation,
-disconnected hosts, and security controls).
+See `guides/_shared/how-to/configure-catalogue-enterprise-distribution.md` for
+the full procedure: configuring the coordinates, regenerating
+`install-defaults.toml`, adding a CI drift check, offline and air-gapped
+environments, and disabling the bootstrap.
 
 ## Build your own catalogue
 

{agentbundle-0.41.1 → agentbundle-0.43.0}/agentbundle/_data/catalogue-index.schema.json

@@ -116,7 +116,8 @@
                     "youProvide": {"type": "string"},
                     "youReceive": {"type": "string"},
                     "yourDecisions": {"type": "array", "items": {"type": "string"}},
-                    "decisionGateIds": {"type": "array", "items": {"type": "string"}}
+                    "decisionGateIds": {"type": "array", "items": {"type": "string"}},
+                    "youType": {"type": "string", "minLength": 1}
                   }
                 }
               }

{agentbundle-0.41.1 → agentbundle-0.43.0}/agentbundle/_data/catalogue-scaffold/guides/_shared/reference/catalogue-authoring-standards.md

@@ -546,6 +546,10 @@ Every integration must declare what the consuming skill does when the target is
 absent. An agent reading the integration without the target installed needs to
 know how to proceed.
 
+Where the target pack publishes a diagnostic vocabulary, the consuming pack's
+`fallback` repeats that target's diagnostic verbatim rather than paraphrasing
+it, so the receipt an agent states is one the target actually emits.
+
 **Lint and verify:**
 
 ```bash
@@ -613,12 +617,20 @@ Use these fields:
   `confirmed-write`.
 - `scope`: `repo` or `user`.
 - `tagline`: a plain-language summary of at most 120 characters.
-- `contract`: a closed object with one optional member. `useItWhen`,
+- `contract`: a closed object with two optional members. `useItWhen`,
   `youProvide`, and `youReceive` are strings; `yourDecisions` is an array of
   strings. `decisionGateIds` is optional and, when present, is an array of
   `humanGates[].id` strings in the order a reader meets those decisions; it
-  carries identifiers only, never adopter-facing wording. Packs authored before
-  it existed stay valid, because `yourDecisions` remains required.
+  carries identifiers only, never adopter-facing wording. `youType` is optional
+  and, when present, is a non-empty string holding the literal first thing a
+  person types to start the journey — one utterance, exactly as a reader would
+  send it, not a description of it. Packs authored before either field existed
+  stay valid, because `yourDecisions` remains required.
+
+  The contract is closed, so a field it does not name is rejected. Adding one is
+  a change to `journey_validator.py`, this standard, and
+  `web/src/lib/journey-schema.ts` together — Zod strips an undeclared key, so a
+  field missing from the web schema can never reach the published page.
 
 Malformed YAML, a missing required field, or a field with the wrong type stops index
 generation before any output is replaced.

{agentbundle-0.41.1 → agentbundle-0.43.0}/agentbundle/_data/catalogue-scaffold/manifest.json

@@ -1,6 +1,6 @@
 {
   "files": {
-    "guides/_shared/reference/catalogue-authoring-standards.md": "4e8bf28a1c4a6861bcfb3028a971163e0250c7db67be2fc32b6ea23f5d1fd547",
+    "guides/_shared/reference/catalogue-authoring-standards.md": "72771324354ff29a4bf9072f48236e537bc680421785d700d2a3308d562777cc",
     "guides/_shared/reference/catalogue-ci-contract.md": "fae793ab47989b6dd3c731afcb0b4cda21c7d08bbe7fa40fca6d3abb3d158141",
     "packs/AGENTS.md": "c20af03f72b4c25c032ba5c15299eadaa0b41442c92d1cf621dde042cf9ff8db",
     "packs/README.md": "d2de5f9556f4c8e521103474bde74636e02cc805f9bf5312a3a61a1f3eb45d8f",

{agentbundle-0.41.1 → agentbundle-0.43.0}/agentbundle/_data/close_work.py

@@ -38,6 +38,14 @@ IMMEDIATE_DISPOSITIONS = frozenset(
 POST_CLOSEOUT_RESULTS = frozenset(
     {"Cooling", "Retained", "Retired", "Reclassified", "ExternalAdvisory"}
 )
+_COMPLETION_RECEIPT_DELIVERY_ID_RE = r"^[a-z0-9][a-z0-9-]{0,127}$"
+_COMPLETION_RECEIPT_EVENTS = ("merge", "release", "acceptance")
+_COMPLETION_RECEIPT_EVIDENCE_REF_RE = (
+    r"^(?:commit:[0-9a-f]{40}|pr:[0-9]+|run:[0-9]+)$"
+)
+_COMPLETION_RECEIPT_OUTCOMES = frozenset(
+    {"completed", "abandoned", "superseded"}
+)
 _ISSUED_CONFIRMATIONS: dict[str, object] = {}
 _ISSUED_PREVIEWS: dict[str, object] = {}
 _CONFIRMED_PREVIEWS: set[str] = set()
@@ -722,11 +730,29 @@ def plan_completion_receipt(
     if binding is None or binding.resource != compatible_surface:
         return ReceiptResult("authorization-required")
     try:
+        receipt_delivery_id = _bounded_text("delivery_id", delivery_id)
+        receipt_outcome = _bounded_text("outcome", outcome)
+        receipt_completion_event = _bounded_text(
+            "completion_event", completion_event
+        )
+        receipt_evidence_ref = _bounded_text("evidence_ref", evidence_ref)
+        if not re.fullmatch(
+            _COMPLETION_RECEIPT_DELIVERY_ID_RE, receipt_delivery_id
+        ):
+            raise ValueError("delivery_id violates the lifecycle-record grammar")
+        if receipt_outcome not in _COMPLETION_RECEIPT_OUTCOMES:
+            raise ValueError("outcome is not a completion-receipt outcome")
+        if receipt_completion_event not in _COMPLETION_RECEIPT_EVENTS:
+            raise ValueError("completion_event is not a lifecycle-record event")
+        if not re.fullmatch(
+            _COMPLETION_RECEIPT_EVIDENCE_REF_RE, receipt_evidence_ref
+        ):
+            raise ValueError("evidence_ref violates the lifecycle-record grammar")
         receipt = CompletionReceipt(
-            delivery_id=_bounded_text("delivery_id", delivery_id),
-            outcome=_bounded_text("outcome", outcome),
-            completion_event=_bounded_text("completion_event", completion_event),
-            evidence_ref=_bounded_text("evidence_ref", evidence_ref),
+            delivery_id=receipt_delivery_id,
+            outcome=receipt_outcome,
+            completion_event=receipt_completion_event,
+            evidence_ref=receipt_evidence_ref,
         )
     except ValueError:
         return ReceiptResult("receipt-evidence-required")

{agentbundle-0.41.1 → agentbundle-0.43.0}/agentbundle/_data/cooling.py

@@ -60,6 +60,7 @@ _TRANSITIONS = frozenset(
         (("retain-exception", "Retained"), ("retain-exception", "Retained")),
         (("retain-exception", "Retained"), ("cool-30-days", "Cooling")),
         (("retain-exception", "Retained"), ("retain-exception", "Retired")),
+        (("retain-exception", "Retained"), ("retain-exception", "Reclassified")),
         (("retain-exception", "Retained"), ("retain-exception", "ExternalAdvisory")),
     }
 )
@@ -328,7 +329,7 @@ def validate_payload(payload: object) -> CoolingResult:
         not _is_one_of(payload["disposition"], {"cool-30-days", "retain-exception"})
         or not _is_one_of(
             payload["post_closeout_result"],
-            {"Cooling", "Retained", "Retired", "ExternalAdvisory"},
+            {"Cooling", "Retained", "Retired", "Reclassified", "ExternalAdvisory"},
         )
     ):
         return CoolingResult(code="record-invalid")
@@ -735,7 +736,10 @@ def load_record(root: Path, path: Path) -> CoolingResult:
             root, path, max_bytes=MAX_RECORD_BYTES
         )
         result = parse_record_bytes(raw)
-    except (ImportError, OSError, ValueError, RecursionError):
+    except ImportError:
+        # The confinement authority is unavailable, so no record can be judged.
+        return CoolingResult(code="cooling-state-unavailable")
+    except (OSError, ValueError, RecursionError):
         return CoolingResult(code="record-invalid")
     if (
         result.code is not None
@@ -910,3 +914,38 @@ def review_exception(
         candidates=candidates,
         authority_binding=authority_binding,
     )
+
+
+def reclassify_record(
+    record: CoolingRecord,
+    acceptance: object,
+    *,
+    root: Path,
+    candidates: object,
+    authority_binding: object,
+) -> CoolingResult:
+    """Persist a retained record with its supplied durable-owner acceptance.
+
+    `acceptance` IS the exception block. It is deliberately NOT unwrapped from a
+    carrier the way `review_exception` reads `renew`'s attestation: that seam
+    validates only the nested value, so a carrier could hold keys outside the
+    envelope and still persist. Reclassification refuses those instead.
+    """
+    if not _exception_is_valid(acceptance):
+        return CoolingResult(code="exception-envelope-invalid")
+    try:
+        proposed = _proposed_record(
+            record,
+            disposition="retain-exception",
+            post_closeout_result="Reclassified",
+            exception=dict(acceptance),
+        )
+    except (TypeError, ValueError):
+        return CoolingResult(code="exception-envelope-invalid")
+    return update_record(
+        root=root,
+        prior=record,
+        proposed=proposed,
+        candidates=candidates,
+        authority_binding=authority_binding,
+    )