agentbundle 0.33.3__tar.gz → 0.35.0__tar.gz

{agentbundle-0.33.3/agentbundle.egg-info → agentbundle-0.35.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentbundle
-Version: 0.33.3
+Version: 0.35.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,17 +34,42 @@ python -m pip install agentbundle
 
 Requires Python 3.11+. Runs on macOS, Linux, and Windows.
 
-## What's new in 0.33.3
+## What's new in 0.35.0
 
-`agentbundle catalogue self-host --write` now updates writable existing files
-without attempting owner-only timestamp or mode changes. This supports CI and
-development checkouts where projected files are owned by a different user;
-ownership, inode, and mode remain intact, while `--check` continues to report
-mode drift that the writer cannot repair.
+**Installs now work on corporate networks that inspect TLS.** If your employer
+runs a proxy that re-signs HTTPS traffic, an install used to fail like this and
+leave you nothing to act on:
 
-The Windows compatibility command covers AgentBundle and pack portability;
-CredBroker maintainers should run that package's test suite separately on
-Windows.
+```
+install: Failed to fetch catalogue archive: … —
+  [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:
+  unable to get local issuer certificate
+```
+
+The certificate authority your IT team installed is in the operating system's
+trust store, and Python does not read that store on macOS. AgentBundle now
+recovers on its own:
+
+```
+agentbundle: certificate verification failed for github.com;
+  retrying with operating-system trust anchors
+```
+
+Verification stays strict throughout — the retry *adds* trust anchors and never
+removes one, and no flag or environment variable can disable verification. Only
+the administrator keychain is read; your login keychain never is, because it is
+writable without administrator rights. Set `AGENTBUNDLE_NO_SYSTEM_TRUST=1` to
+opt out and see the underlying error.
+
+`AGENTBUNDLE_CA_BUNDLE` also works on `git+https://` sources now — previously
+only the `catalogue+https://` and `archive+https://` forms read it, so following
+the documentation did not help. `SSL_CERT_FILE`, `SSL_CERT_DIR`, and
+`REQUESTS_CA_BUNDLE` are honoured there too. See
+[Corporate networks](#corporate-networks) below.
+
+When a fetch still fails, the error names the likely cause and ordered next
+steps, and the request now carries a 30-second timeout so a proxy that accepts
+the connection and never answers fails instead of hanging.
 
 **Install into a repo** — so everyone who clones it gets the pack. `core` is the flagship pack, the loop itself:
 
@@ -263,6 +288,10 @@ agentbundle catalogue init --target /path/to/new-catalogue
 
 Scaffolds `catalogue.toml`, the required directory tree (`packs/`, `profiles/`, `contracts/`, `.claude-plugin/`), and a starter `marketplace.json`. Skips files that already exist; reports conflicts without overwriting. Pass `--dry-run` to preview.
 
+After initialization, use `agentbundle catalogue contracts list` to find the
+contract names bundled with your installed version. `show` prints one contract;
+`export --output <dir>` copies the full public set for offline reference.
+
 **Bootstrap a self-hosted enterprise catalogue** from an existing source:
 
 ```bash
@@ -481,6 +510,51 @@ or `WORKSPACE_MCP_DISPATCHED_ITEM` (`ini_slug/type:slug`) for non-FSM shaping
 items. Setting neither gives discovery-only mode (git writes disabled). Setting
 both is unsupported — only one selects the mode.
 
+## Corporate networks
+
+macOS is the only platform where Python ignores the operating system's trust
+store, which is why the automatic fallback above is macOS-only:
+
+| Platform | Trust source | Needs anything from you? |
+| --- | --- | --- |
+| **Windows** | Python loads the Windows `CA` and `ROOT` stores and honours each certificate's trust settings | No — a root pushed by Group Policy or Intune already works |
+| **Linux** | OpenSSL reads `/etc/ssl/certs` | No, once the authority is installed there |
+| **WSL** | Same as Linux — a WSL distribution does **not** inherit the Windows certificate store | **Yes** — see below |
+| **macOS** | OpenSSL reads a PEM file; the keychain is invisible to it | No — this is the case the fallback handles |
+
+If your IT team gives you a CA bundle, point AgentBundle at it directly:
+
+```bash
+export AGENTBUNDLE_CA_BUNDLE=/path/to/corporate-ca.pem
+agentbundle install --pack core
+```
+
+On `git+https://` sources that bundle is **added** to the default trust store, so
+a bundle holding only your private authority still verifies public hosts. On
+`catalogue+https://` and `archive+https://` it **replaces** the store, pinning
+verification to your own authority — useful for an internal Artifactory mirror.
+
+**WSL** is the case most likely to catch out a Windows-standardised organisation:
+your IT team pushes the authority to Windows, Windows tools pick it up, and
+nothing inside the WSL distribution does. Export it from Windows (Certificate
+Manager → Trusted Root Certification Authorities → Export as Base-64 X.509), then
+install it in the distribution:
+
+```bash
+sudo cp corporate-ca.crt /usr/local/share/ca-certificates/
+sudo update-ca-certificates
+```
+
+Two things no certificate configuration can fix: a proxy that requires Kerberos
+or NTLM authentication, and an egress allowlist that permits `github.com` but not
+`codeload.github.com` — a GitHub archive fetch redirects across both hosts.
+
+A note on virtualenvs, since it comes up: creating one does **not** change TLS
+trust. A virtualenv inherits its base interpreter's certificate store unchanged.
+If an install works under one `python3` and not another, the interpreters differ,
+not the environment — compare them with
+`python3 -c "import ssl; print(ssl.get_default_verify_paths())"`.
+
 ## Credentials
 
 `agentbundle` doesn't resolve secrets. Credentialed skills use [`credbroker`](https://pypi.org/project/credbroker/), a standalone resolver that keeps cleartext out of the model's reach.

{agentbundle-0.33.3 → agentbundle-0.35.0}/README-pypi.md

@@ -14,17 +14,42 @@ python -m pip install agentbundle
 
 Requires Python 3.11+. Runs on macOS, Linux, and Windows.
 
-## What's new in 0.33.3
+## What's new in 0.35.0
 
-`agentbundle catalogue self-host --write` now updates writable existing files
-without attempting owner-only timestamp or mode changes. This supports CI and
-development checkouts where projected files are owned by a different user;
-ownership, inode, and mode remain intact, while `--check` continues to report
-mode drift that the writer cannot repair.
+**Installs now work on corporate networks that inspect TLS.** If your employer
+runs a proxy that re-signs HTTPS traffic, an install used to fail like this and
+leave you nothing to act on:
 
-The Windows compatibility command covers AgentBundle and pack portability;
-CredBroker maintainers should run that package's test suite separately on
-Windows.
+```
+install: Failed to fetch catalogue archive: … —
+  [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:
+  unable to get local issuer certificate
+```
+
+The certificate authority your IT team installed is in the operating system's
+trust store, and Python does not read that store on macOS. AgentBundle now
+recovers on its own:
+
+```
+agentbundle: certificate verification failed for github.com;
+  retrying with operating-system trust anchors
+```
+
+Verification stays strict throughout — the retry *adds* trust anchors and never
+removes one, and no flag or environment variable can disable verification. Only
+the administrator keychain is read; your login keychain never is, because it is
+writable without administrator rights. Set `AGENTBUNDLE_NO_SYSTEM_TRUST=1` to
+opt out and see the underlying error.
+
+`AGENTBUNDLE_CA_BUNDLE` also works on `git+https://` sources now — previously
+only the `catalogue+https://` and `archive+https://` forms read it, so following
+the documentation did not help. `SSL_CERT_FILE`, `SSL_CERT_DIR`, and
+`REQUESTS_CA_BUNDLE` are honoured there too. See
+[Corporate networks](#corporate-networks) below.
+
+When a fetch still fails, the error names the likely cause and ordered next
+steps, and the request now carries a 30-second timeout so a proxy that accepts
+the connection and never answers fails instead of hanging.
 
 **Install into a repo** — so everyone who clones it gets the pack. `core` is the flagship pack, the loop itself:
 
@@ -243,6 +268,10 @@ agentbundle catalogue init --target /path/to/new-catalogue
 
 Scaffolds `catalogue.toml`, the required directory tree (`packs/`, `profiles/`, `contracts/`, `.claude-plugin/`), and a starter `marketplace.json`. Skips files that already exist; reports conflicts without overwriting. Pass `--dry-run` to preview.
 
+After initialization, use `agentbundle catalogue contracts list` to find the
+contract names bundled with your installed version. `show` prints one contract;
+`export --output <dir>` copies the full public set for offline reference.
+
 **Bootstrap a self-hosted enterprise catalogue** from an existing source:
 
 ```bash
@@ -461,6 +490,51 @@ or `WORKSPACE_MCP_DISPATCHED_ITEM` (`ini_slug/type:slug`) for non-FSM shaping
 items. Setting neither gives discovery-only mode (git writes disabled). Setting
 both is unsupported — only one selects the mode.
 
+## Corporate networks
+
+macOS is the only platform where Python ignores the operating system's trust
+store, which is why the automatic fallback above is macOS-only:
+
+| Platform | Trust source | Needs anything from you? |
+| --- | --- | --- |
+| **Windows** | Python loads the Windows `CA` and `ROOT` stores and honours each certificate's trust settings | No — a root pushed by Group Policy or Intune already works |
+| **Linux** | OpenSSL reads `/etc/ssl/certs` | No, once the authority is installed there |
+| **WSL** | Same as Linux — a WSL distribution does **not** inherit the Windows certificate store | **Yes** — see below |
+| **macOS** | OpenSSL reads a PEM file; the keychain is invisible to it | No — this is the case the fallback handles |
+
+If your IT team gives you a CA bundle, point AgentBundle at it directly:
+
+```bash
+export AGENTBUNDLE_CA_BUNDLE=/path/to/corporate-ca.pem
+agentbundle install --pack core
+```
+
+On `git+https://` sources that bundle is **added** to the default trust store, so
+a bundle holding only your private authority still verifies public hosts. On
+`catalogue+https://` and `archive+https://` it **replaces** the store, pinning
+verification to your own authority — useful for an internal Artifactory mirror.
+
+**WSL** is the case most likely to catch out a Windows-standardised organisation:
+your IT team pushes the authority to Windows, Windows tools pick it up, and
+nothing inside the WSL distribution does. Export it from Windows (Certificate
+Manager → Trusted Root Certification Authorities → Export as Base-64 X.509), then
+install it in the distribution:
+
+```bash
+sudo cp corporate-ca.crt /usr/local/share/ca-certificates/
+sudo update-ca-certificates
+```
+
+Two things no certificate configuration can fix: a proxy that requires Kerberos
+or NTLM authentication, and an egress allowlist that permits `github.com` but not
+`codeload.github.com` — a GitHub archive fetch redirects across both hosts.
+
+A note on virtualenvs, since it comes up: creating one does **not** change TLS
+trust. A virtualenv inherits its base interpreter's certificate store unchanged.
+If an install works under one `python3` and not another, the interpreters differ,
+not the environment — compare them with
+`python3 -c "import ssl; print(ssl.get_default_verify_paths())"`.
+
 ## Credentials
 
 `agentbundle` doesn't resolve secrets. Credentialed skills use [`credbroker`](https://pypi.org/project/credbroker/), a standalone resolver that keeps cleartext out of the model's reach.

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

@@ -407,6 +407,23 @@ every optional pack.
 
 ---
 
+## 12. Bundled contract inspection
+
+List, inspect, or export the contracts bundled with the running AgentBundle version
+without network access:
+
+```bash
+agentbundle catalogue contracts list
+agentbundle catalogue contracts show <name>
+agentbundle catalogue contracts export --output <dir>
+```
+
+`list` and `show` are read-only. `export` writes one regular file per listed contract
+to the selected directory. These are reference copies only. They do not override the
+contracts used for validation by this agentbundle version.
+
+---
+
 ## Journey format
 
 > **Not yet available.** Wave 4 of the catalogue-contracts initiative will define the

{agentbundle-0.33.3 → agentbundle-0.35.0}/agentbundle/_data/catalogue-scaffold/manifest.json

@@ -1,6 +1,6 @@
 {
   "files": {
-    "guides/_shared/reference/catalogue-authoring-standards.md": "ff4bdc203affda0a2f41641c1155b3f4e90aade022e122999a82e7093e94d2ee",
+    "guides/_shared/reference/catalogue-authoring-standards.md": "3217e6bfcc15dc116d40e1b327b6bf19b66212c7e13553e42966f9982b3c3487",
     "guides/_shared/reference/catalogue-ci-contract.md": "fae793ab47989b6dd3c731afcb0b4cda21c7d08bbe7fa40fca6d3abb3d158141",
     "packs/AGENTS.md": "9bfeda4069826e518a4f4fdae45bd40f4393c1c5aaf146149d3eb4aece30be83",
     "packs/README.md": "d2de5f9556f4c8e521103474bde74636e02cc805f9bf5312a3a61a1f3eb45d8f",

agentbundle-0.35.0/agentbundle/_data/public-contracts.txt

@@ -0,0 +1,12 @@
+adapter.schema.json
+adapter.toml
+catalogue.schema.json
+guide.schema.json
+marketplace-entry.schema.json
+pack.schema.json
+plugin-manifest.derived.schema.json
+plugin-manifest.schema.json
+profile.schema.json
+skill-manifest.schema.json
+skill.schema.json
+target-vocab.toml

{agentbundle-0.33.3 → agentbundle-0.35.0}/agentbundle/build/projection_io.py

@@ -15,6 +15,10 @@ from contextlib import contextmanager
 from pathlib import Path
 from typing import Literal
 
+from agentbundle.safety import _is_reparse_point as _safety_is_reparse_point
+from agentbundle.safety import _secure_dir_fd_available as _safety_secure_dir_fd_available
+from agentbundle.safety import _write_all as _safety_write_all
+
 
 class ProjectionTypeError(OSError):
     """A projected target exists but is not a regular file."""
@@ -30,9 +34,11 @@ def render_diagnostic_path(path: Path) -> str:
 
 
 def _secure_dir_fd_available() -> bool:
-    return os.name == "posix" and all(
-        hasattr(os, name) for name in ("O_DIRECTORY", "O_NOFOLLOW")
-    )
+    """Re-exported from ``agentbundle.safety`` — see that module for the rule.
+
+    Kept as a module-level name so tests can monkeypatch it here.
+    """
+    return _safety_secure_dir_fd_available()
 
 
 def _validate_relative(relative: Path) -> None:
@@ -40,10 +46,7 @@ def _validate_relative(relative: Path) -> None:
         raise ValueError(f"projection path must stay relative to its base: {relative}")
 
 
-def _is_reparse_point(path_stat: os.stat_result) -> bool:
-    attributes = getattr(path_stat, "st_file_attributes", 0)
-    reparse_flag = getattr(stat, "FILE_ATTRIBUTE_REPARSE_POINT", 0)
-    return bool(attributes & reparse_flag)
+_is_reparse_point = _safety_is_reparse_point
 
 
 def _validate_fallback_path(
@@ -159,14 +162,7 @@ def open_directory_no_follow(base: Path, relative: Path) -> Iterator[int | None]
         os.close(base_fd)
 
 
-def _write_all(file_descriptor: int, content: bytes) -> None:
-    """Write all ``content`` to an open descriptor."""
-    view = memoryview(content)
-    while view:
-        written = os.write(file_descriptor, view)
-        if written == 0:
-            raise OSError(errno.EIO, "projection write made no progress")
-        view = view[written:]
+_write_all = _safety_write_all
 
 
 def _read_bounded(