apcore-cli 0.6.0__tar.gz → 0.7.0__tar.gz

apcore_cli-0.7.0/.github/workflows/ci.yml

@@ -0,0 +1,62 @@
+name: CI
+
+permissions:
+  contents: read
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+jobs:
+  test:
+    name: Test on Python ${{ matrix.python-version }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        # Pin CI to a single, consistent Python version to reduce version-related
+        # test flakiness. Use 3.12 for CI stability; expand matrix later if desired.
+        python-version: ["3.12"]
+
+    steps:
+    - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+
+    - name: Checkout apcore-cli spec repo (conformance fixtures)
+      uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+      with:
+        repository: aiperceivable/apcore-cli
+        path: .apcore-cli-spec
+
+    - name: Set up Python
+      uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
+      with:
+        python-version: ${{ matrix.python-version }}
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@v5
+
+    # `--extra dev` pulls pytest, ruff, pre-commit, mypy, apdev; `--extra toolkit`
+    # brings in apcore-toolkit >= 0.5.0. apcore >= 0.19.0 comes from the main
+    # `dependencies` section and is installed unconditionally. Toolkit must be
+    # importable for tests/test_toolkit_integration.py (which uses
+    # `patch("apcore_toolkit.BindingLoader", ...)` — patch resolves the target
+    # at import time and fails if the module is absent).
+    - name: Install dependencies (apcore, apcore-toolkit, dev extras)
+      run: |
+        uv sync --extra dev --extra toolkit
+
+    # Single pre-commit invocation covers ruff lint + ruff-format + apdev
+    # (check-chars, check-imports). Matches the TypeScript CI pattern at
+    # ../apcore-cli-typescript/.github/workflows/ci.yml which likewise runs
+    # `pre-commit run --all-files` as the lint gate.
+    - name: Run pre-commit (ruff + apdev hooks)
+      run: |
+        uv run pre-commit run --all-files
+
+    - name: Run tests
+      env:
+        APCORE_CLI_SPEC_REPO: ${{ github.workspace }}/.apcore-cli-spec
+      run: |
+        uv run pytest

{apcore_cli-0.6.0 → apcore_cli-0.7.0}/.gitignore

@@ -16,3 +16,4 @@ venv/
 env/
 .env
 .forge
+.mypy_cache/

{apcore_cli-0.6.0 → apcore_cli-0.7.0}/CHANGELOG.md

@@ -6,6 +6,34 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 
+## [0.7.0] - 2026-04-23
+
+### Changed
+
+- **Dependency bump**: requires `apcore >= 0.18.0` (was `>= 0.17.1`). Aligns with upstream `apcore 0.18.0` and `apcore-toolkit 0.4.2` breaking changes.
+- **`MAX_MODULE_ID_LENGTH` 128 → 192**: `validate_module_id()` and all references updated to the new 192-character limit introduced in `apcore 0.18.0` (`apcore.registry.registry.MAX_MODULE_ID_LENGTH`).
+- **`describe-pipeline` renders `StrategyInfo`**: `executor.describe_pipeline(strategy)` now returns a `StrategyInfo` dataclass (`name`, `step_count`, `step_names`, `description`). `strategy.py` updated to use `StrategyInfo` fields; header line is `Pipeline: {info.name} ({info.step_count} steps)`. Falls back gracefully to the legacy `_resolve_strategy_name` path when `describe_pipeline` is unavailable.
+- **CI — spec-repo checkout**: `.github/workflows/ci.yml` now checks out `aiperceivable/apcore-cli` into `.apcore-cli-spec/` and exposes it to `pytest` via `APCORE_CLI_SPEC_REPO`. Mirrors the pattern established in `apcore-python` / `apcore-cli-typescript`.
+
+### Added
+
+- **`create_cli(app=...)` parameter**: `create_cli()` accepts an optional `app: APCore` unified client (introduced in `apcore 0.18.0`). `app` is mutually exclusive with `registry`/`executor` (raises `ValueError`). When `app` is provided, `registry` and `executor` are extracted from `app.registry` and `app.executor`. Filesystem discovery is skipped if `app.registry` already contains registered modules; otherwise normal discovery proceeds into `app.registry`.
+- **Cross-language conformance test harness** (`tests/conformance/`) consuming the shared apcli-visibility fixtures from the `aiperceivable/apcore-cli` spec repo (`conformance/fixtures/apcli-visibility/`). Behavioral assertions (apcli group visibility, registered subcommand set for `include`/`exclude` modes, always-registered `exec`) run today across all five canonical scenarios (`standalone-default`, `embedded-default`, `cli-override`, `env-override`, `yaml-include`). Byte-matching against `expected_help.txt` is marked `xfail` until Click's `HelpFormatter` is replaced with a canonical clap v4 / GNU-style emitter, tracked for parity with `apcore-cli-typescript/src/canonical-help.ts`.
+- **`APCORE_CLI_SPEC_REPO` env var** — overrides the spec-repo lookup path for conformance fixtures. Defaults to a sibling checkout (`../apcore-cli/`). Tests are skipped (not failed) when the spec repo is absent.
+- **FE-12: Module Exposure Filtering** — Declarative control over which discovered modules are exposed as CLI commands.
+  - `ExposureFilter` class in `exposure.py` with `is_exposed(module_id)` and `filter_modules(ids)` methods.
+  - Three modes: `all` (default), `include` (whitelist), `exclude` (blacklist) with glob-pattern matching.
+  - `ExposureFilter.from_config(dict)` classmethod for loading from `apcore.yaml` `expose` section.
+  - `create_cli(expose=...)` parameter accepting `dict` or `ExposureFilter` instance.
+  - `list --exposure {exposed,hidden,all}` filter flag in discovery commands.
+  - `GroupedModuleGroup._build_group_map()` integration: calls `ExposureFilter.is_exposed()` to filter command registration.
+  - `ConfigResolver` gains `expose.*` config keys.
+  - 4-tier config precedence: `CliConfig.expose` > `--expose-mode` CLI flag > env var > `apcore.yaml`.
+  - Hidden modules remain invocable via `exec <module_id>`.
+- New file: `exposure.py`.
+
+---
+
 ## [0.6.0] - 2026-04-06
 
 ### Changed

apcore_cli-0.7.0/CLAUDE.md

@@ -0,0 +1,60 @@
+# CLAUDE.md — apcore-cli-python
+
+## Build & Test
+
+- `pytest` — run all tests. **Must pass before considering any task complete.**
+- `pytest --cov` — run with coverage report.
+- `ruff check .` — lint check.
+- `ruff format .` — format all code. **Run after every code change.**
+
+## Code Style
+
+- Python 3.11+ with `from __future__ import annotations`.
+- All code must pass `ruff check` and `ruff format --check`.
+- Type annotations on all public function signatures.
+- Use `click.echo()` for user-facing output, `logger.*` for debug/diagnostic output.
+- Prefer `sys.exit(code)` with exit code constants over raising exceptions for CLI errors.
+
+## Project Conventions
+
+- Spec repo (single source of truth): `../apcore-cli/docs/`
+- Package structure: `src/apcore_cli/` with `__init__.py` exporting `__version__` only.
+- Entry point: `apcore_cli.__main__:main`.
+- Security modules live in `src/apcore_cli/security/` sub-package.
+- ConfigResolver.DEFAULTS values are Python-typed (str, int, bool).
+- Tests organized by module: `tests/test_<module>.py`, security tests in `tests/test_security/`.
+
+## Environment
+
+- Python >= 3.11
+- Key dependencies: click >= 8.1, rich >= 13.0, jsonschema >= 4.20, pyyaml >= 6.0, keyring >= 24, cryptography >= 41
+- Runtime: apcore >= 0.19.0 (v0.7.0 bump, was 0.17.1)
+- Optional: apcore-toolkit >= 0.4 (install via `pip install apcore-cli[toolkit]`)
+- Dev: pytest, pytest-asyncio, pytest-cov, mypy, ruff
+
+## v0.7.0 Conventions
+
+- Public surface (`__init__.py`): `__version__`, `create_cli`, `ExposureFilter`,
+  `ApcliGroup`, `ApcliMode`, `RESERVED_GROUP_NAMES`, `CliApprovalHandler`,
+  `resolve_refs`, `schema_to_click_options`, `format_exec_result`,
+  `ConfigResolver`, `AuditLogger`, `AuthProvider`, `ConfigEncryptor`, `Sandbox`,
+  plus error classes (AuthenticationError, ConfigDecryptionError,
+  ModuleExecutionError, ApprovalTimeoutError, ApprovalDeniedError).
+  Non-listed symbols (e.g. `GroupedModuleGroup`) must be imported via full
+  submodule path (e.g., `from apcore_cli.cli import GroupedModuleGroup`).
+- ExposureFilter + `expose=` kwarg on create_cli (FE-12).
+- `extra_commands=[...]` kwarg on create_cli as the FE-11 extension point (with
+  collision detection against RESERVED_GROUP_NAMES — `BUILTIN_COMMANDS` retired v0.7.0).
+- Default click Group class is `GroupedModuleGroup` (multi-level grouping since v0.3.0).
+- All apcore-cli commands live under the `apcli` group (FE-13). Deprecation shims
+  remain at root level for back-compat until v0.8.
+- `system_cmd` module registers runtime system commands (health/usage/enable/disable/
+  reload/config) — FE-11.
+- `strategy` module registers describe-pipeline + --strategy flag — FE-11.
+- `validate` module + --dry-run flag — FE-11.
+- `CliApprovalHandler` async protocol (request_approval/check_approval) — FE-11 §3.5.1.
+- Config Bus namespace registration at package import time (apcore >= 0.15.0).
+- New env vars (v0.6.0): APCORE_CLI_APPROVAL_TIMEOUT, APCORE_CLI_STRATEGY, APCORE_CLI_GROUP_DEPTH.
+- New config keys (v0.6.0): cli.approval_timeout, cli.strategy, cli.group_depth.
+- New exit codes from apcore 0.17.1: CONFIG_BIND_ERROR (65), CONFIG_MOUNT_ERROR (66),
+  ERROR_FORMATTER_DUPLICATE (70), CONFIG_NAMESPACE_* (78).

apcore_cli-0.7.0/LICENSE

@@ -0,0 +1,193 @@
+                                 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 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, as submitted to the 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 designated in writing by the copyright owner as "Not a
+      Contribution."
+
+      "Contributor" shall mean Licensor and any Legal Entity on behalf of
+      whom a Contribution has been received by the Licensor and included
+      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 the combined work (in which such
+      Contribution(s) has been submitted). If You institute patent litigation
+      against any entity (including a cross-claim or counterclaim in a
+      lawsuit) alleging that the Work or any other 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, You must include a readable copy of the
+          attribution notices contained within such NOTICE file, 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 in addition 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 license statement for Your modifications and
+      may provide additional grant of rights to use, copy, modify, merge,
+      publish, distribute, sublicense, and/or sell copies of the
+      Contribution(s) and such Derivative Works.
+
+   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 conditions of TITLE,
+      NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR
+      PURPOSE. You are solely responsible for determining the
+      appropriateness of using or reproducing 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 exemplary 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 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 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 offer such
+      obligations 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 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 format in use. Please also attach a
+      separate file called "NOTICE" with the information required
+      by Section 4(d).
+
+   Copyright 2024 APCore Contributors
+
+   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.

apcore_cli-0.7.0/Makefile

@@ -0,0 +1,30 @@
+.PHONY: test test-cov lint fmt fmt-check check clean
+
+# Run all tests (no coverage; same as `pytest`).
+test:
+	pytest --tb=short -q
+
+# Run tests with coverage report (D5-002 cross-SDK coverage wiring).
+# Mirrors apcore-cli-rust `make coverage` and apcore-cli-typescript
+# `pnpm run test:cov`. Configuration lives in pyproject.toml under
+# [tool.coverage.*] (source, fail_under, show_missing).
+test-cov:
+	pytest --cov=apcore_cli --cov-report=term-missing --cov-report=html
+
+# Lint with ruff.
+lint:
+	ruff check src tests
+
+# Format code with ruff. Run after every code change (CLAUDE.md).
+fmt:
+	ruff format src tests
+
+# Check formatting without writing.
+fmt-check:
+	ruff format --check src tests
+
+# Pre-commit / pre-merge gate.
+check: fmt-check lint test
+
+clean:
+	rm -rf .coverage htmlcov build dist *.egg-info .pytest_cache .ruff_cache