apcore-toolkit 0.4.2__tar.gz → 0.6.0__tar.gz

{apcore_toolkit-0.4.2 → apcore_toolkit-0.6.0}/.gitignore

@@ -11,6 +11,10 @@ build/
 .DS_Store
 .ruff_cache/
 .pytest_cache/
+.mypy_cache/
+.pyright_cache/
+htmlcov/
+coverage.xml
 .coverage
 .venv/
 venv/

{apcore_toolkit-0.4.2 → apcore_toolkit-0.6.0}/CHANGELOG.md

@@ -2,6 +2,63 @@
 
 All notable changes to this project will be documented in this file.
 
+
+## [0.6.0] - 2026-05-07
+
+### Changed
+
+- **`apcore` minimum version bumped from 0.20.0 to 0.21.0** — `pyproject.toml` `dependencies` now requires `apcore>=0.21.0`. Toolkit only imports stable apcore surface (`ModuleAnnotations`, `DEFAULT_ANNOTATIONS`, `ModuleExample`, `Registry`, `ErrorCodes`, `parse_docstring`, `errors.ModuleError`); the 0.21.0 additions (`discoverable` field on `ModuleAnnotations`, `PreviewResult`, `Change`, `ephemeral.*` namespace) are automatically handled — `ModuleAnnotations.from_dict()` picks up `discoverable` transparently, and `dataclasses.asdict()` / `dataclasses.replace()` propagate the new field without code changes. `AIEnhancer` derives its field set from `dataclasses.fields(ModuleAnnotations)` at import time, so it also picks up `discoverable` automatically. Full pytest suite verified against apcore 0.21.0.
+- **`apcore` minimum version bumped from 0.19.0 to 0.20.0** — `pyproject.toml` `dependencies` now requires `apcore>=0.20.0`. Toolkit only imports stable apcore surface (`ModuleAnnotations`, `DEFAULT_ANNOTATIONS`, `ModuleExample`, `Registry`, `ErrorCodes`, `parse_docstring`, `errors.ModuleError`); none of these were affected by 0.20.0 changes. Full pytest suite (585 passed) verified against apcore 0.20.0.
+
+### Added
+
+- **Surface-aware formatters** (refs aiperceivable/apcore-toolkit#13) — `format_module`, `format_schema`, `format_modules` for rendering `ScannedModule` and JSON Schema for specific consumer surfaces. Four styles for `format_module`: `markdown` (LLM context), `skill` (drop-in `.claude/skills/<id>/SKILL.md` or `.gemini/skills/<id>/SKILL.md` body with minimal `name` + `description` frontmatter — no vendor-specific extensions), `table-row` (CLI listing), `json` (programmatic). `format_schema` styles: `prose`, `table`, `json`. `format_modules` adds optional `group_by="tag" | "prefix"`. `display=True` (default) prefers the `ScannedModule.display` overlay over raw fields. Lives in `apcore_toolkit.formatting.surface`; re-exported at the top-level package.
+- **Annotation-table cross-SDK alignment** — `format_module(style="markdown" | "skill")` `## Behavior` table now emits only fields that differ from `ModuleAnnotations()` defaults, sorts rows alphabetically by snake_case key, and renders bool values as lowercase `true`/`false`. The section is omitted entirely when every annotation field matches its default. Closes the byte-equality gap with the TypeScript and Rust SDKs.
+
+### Changed
+
+- **`infer_annotations_from_method` canonical mapping** (refs aiperceivable/apcore-toolkit#11) — `HEAD` and `OPTIONS` now map to `readonly=true` (without `cacheable=true`), matching the canonical mapping declared in `apcore-toolkit/docs/features/scanning.md` and aligning with the existing Rust SDK. Previously these methods returned default annotations.
+
+## [0.5.0] - 2026-04-21
+
+### Added
+
+- **`BindingLoader`** (`apcore_toolkit.binding_loader`) — parses `.binding.yaml` files back into `ScannedModule` objects, the inverse of `YAMLWriter`. Unlike `apcore.BindingLoader`, this is pure data: no target import, no Registry mutation. Enables verification, merging, diffing, and round-trip workflows.
+  - `load(path, *, strict=False)` — single file or directory of `*.binding.yaml`.
+  - `load_data(data, *, strict=False)` — pre-parsed YAML dict.
+  - Loose mode (default): only `module_id + target` required; missing fields use defaults.
+  - Strict mode: additionally requires `input_schema + output_schema`.
+  - `spec_version` validated; missing/unsupported versions WARN but do not fail.
+  - `annotations` parsed via `ModuleAnnotations.from_dict`; malformed values degrade to `None` with WARN.
+  - `examples` entries validated individually; malformed ones skipped with WARN.
+  - `BindingLoadError` exception carries `file_path`, `module_id`, `missing_fields`, `reason`.
+- **`ScannedModule.display`** — new top-level optional field (`dict | None`) holding the sparse display overlay for binding YAML persistence. Distinct from `metadata["display"]` (resolved form produced by `DisplayResolver`).
+- **New feature doc**: `docs/features/binding-loader.md`; `display-overlay.md` and `output-writers.md` updated.
+
+### Changed
+
+- **`YAMLWriter._build_binding`** — emits top-level `display:` key only when `ScannedModule.display is not None` (skip when None keeps output clean).
+- **`serializers.module_to_dict`** — includes `display` key in output.
+- **`AIEnhancer._build_prompt`** — confidence template is now built dynamically from `gaps`. When `annotations` is in gaps, the prompt requests per-field confidence for every `_ANNOTATION_FIELD_VALIDATORS` field (`annotations.readonly`, `annotations.streaming`, `annotations.cache_ttl`, ...). Previously the template hard-coded `{"description": 0.0, "documentation": 0.0}` only, causing all annotation-field confidence lookups to fall back to `0.0` and fail the threshold check — annotation enhancement silently never took effect. Fixes symmetry with `_enhance_module`'s `ann_conf.get(f"annotations.{field_name}", ...)` read path.
+
+### Dependencies
+
+- **`apcore >= 0.19.0`** — picks up the expanded `ModuleAnnotations` (12 fields incl. `streaming`, `cacheable`, `cache_ttl`, `cache_key_fields`, `paginated`, `pagination_style`, `extra`). No toolkit code changes were needed for the type itself — `_build_annotation_field_validators` reflects the updated dataclass automatically.
+
+### Tests
+
+- +34 new tests: 24 for `BindingLoader` (parsing, strict/loose modes, spec_version, file & directory loading, round-trip with `YAMLWriter`), 5 for the prompt confidence block, and 5 hardening tests (display deep-copy, malformed-shape warn, recursive glob, UTF-8 encoding, null-field error wording).
+- Updated `test_field_count` (13 → 14) and `test_all_expected_keys` for the new `display` field.
+- Total suite: 440 tests.
+
+### Hardening (post-review)
+
+- **`BindingLoader`**: warns (rather than silently drops) malformed `display` values that are not a mapping; `load()` gained a `recursive: bool = False` kwarg for nested binding layouts; `read_text` now forces UTF-8 decoding so non-ASCII aliases round-trip on non-UTF-8 locales; required-field validation now rejects wrong-type scalars (e.g. `module_id: 42`, `target: true`) and empty strings in addition to absent/null, matching the Rust loader's contract — error wording is "missing or invalid required fields"; nested `input_schema`/`output_schema`/`metadata` are now deep-copied via `copy.deepcopy` so caller mutation does not leak back into the parsed YAML source graph.
+- **`YAMLWriter`**: `display` is now deep-copied into the emitted binding (defensive parity with the TypeScript/Rust writers) so post-write mutation of `ScannedModule.display` cannot leak into the file. File writes are now atomic: the payload is written to `<name>.<pid>.tmp`, `fsync`ed, then `os.replace`d onto the final path (matches the TypeScript `tmp + rename` and Rust `tmp + sync_all + rename` writers). A process crash mid-write no longer leaves a partial YAML file that `BindingLoader` would fail to parse. A pre-write check refuses to overwrite a symlink at the target path (defence-in-depth against TOCTOU).
+- **`BaseScanner.deduplicate_ids`**: pre-scans all input `module_id`s so generated `_N` suffixes never collide with an ID already present in the input. Input `[a, a, a_2]` now yields `[a, a_3, a_2]` instead of the previous buggy `[a, a_2, a_2]`. Matches the TypeScript and Rust implementations.
+- **`resolve_target` / `RegistryWriter.write`**: new `allowed_prefixes: list[str] | None` kwarg (forwarded from `RegistryWriter.write` through `_to_function_module` to `resolve_target`). When set, `resolve_target` rejects any module path outside the listed prefixes **before** calling `importlib.import_module`, raising `PermissionError`. Mitigates arbitrary-code-execution via forged binding files (e.g. a malicious `target: "os:system"` injected into untrusted YAML). Parity with the TypeScript SDK's `allowedPrefixes` option, adapted to Python's module-name import model. Boundary-aware: `"myapp"` permits `myapp.views` but NOT `myappx.foo`. Rust does not need this because `resolve_target` is parse-only and the `HandlerFactory` is the security boundary.
+- **`ScannedModule.display`**: moved to the END of the dataclass so existing positional `ScannedModule(...)` callers are not broken by the new field.
+
 ## [0.4.1] - 2026-03-25
 
 ### Added

apcore_toolkit-0.6.0/LICENSE

@@ -0,0 +1,185 @@
+                                 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 defined in Section 5, any work of authorship,
+      including the original version of the Work and any modifications or
+      additions to that Work or Derivative Works of the Work, that is
+      intentionally 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 otherwise
+      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 subsequently
+      incorporated 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 combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a cross-claim
+      or counterclaim in a lawsuit) alleging that the Work or any Contribution
+      incorporated within the 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 as an addendum 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 Work and
+      Derivative Works, subject to the conditions of this License.
+
+   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 warranties or 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 choose to 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 conditions 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 such warranty or
+      additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2024 aiperceivable
+
+   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_toolkit-0.4.2 → apcore_toolkit-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: apcore-toolkit
-Version: 0.4.2
+Version: 0.6.0
 Summary: Shared scanner, schema extraction, and output toolkit for apcore framework adapters
 Project-URL: Homepage, https://aiperceivable.com
 Project-URL: Repository, https://github.com/aiperceivable/apcore-toolkit-python
@@ -8,9 +8,10 @@ Project-URL: Documentation, https://github.com/aiperceivable/apcore-toolkit-pyth
 Project-URL: Issues, https://github.com/aiperceivable/apcore-toolkit-python/issues
 Author-email: aiperceivable <tercel.yi@gmail.com>
 License-Expression: Apache-2.0
+License-File: LICENSE
 Keywords: apcore,mcp,openapi,pydantic,scanner,schema,toolkit,yaml
 Requires-Python: >=3.11
-Requires-Dist: apcore>=0.18.0
+Requires-Dist: apcore>=0.21.0
 Requires-Dist: pydantic>=2.0
 Requires-Dist: pyyaml>=6.0
 Provides-Extra: dev
@@ -18,10 +19,12 @@ Requires-Dist: apdev[dev]>=0.2.1; extra == 'dev'
 Requires-Dist: httpx>=0.24; extra == 'dev'
 Requires-Dist: mypy>=1.0; extra == 'dev'
 Requires-Dist: pytest-cov>=4.0; extra == 'dev'
-Requires-Dist: pytest>=7.0; extra == 'dev'
-Requires-Dist: ruff>=0.1; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.9; extra == 'dev'
 Provides-Extra: http-proxy
 Requires-Dist: httpx>=0.24; extra == 'http-proxy'
+Provides-Extra: json-schema
+Requires-Dist: jsonschema>=4.0; extra == 'json-schema'
 Description-Content-Type: text/markdown
 
 <div align="center">
@@ -48,6 +51,8 @@ pip install apcore-toolkit
 | `ScannedModule` | Canonical dataclass representing a scanned endpoint |
 | `BaseScanner` | Abstract base class for framework scanners with filtering and deduplication |
 | `YAMLWriter` | Generates `.binding.yaml` files for `apcore.BindingLoader` |
+| `BindingLoader` | Parses `.binding.yaml` files back into `ScannedModule` objects (pure-data inverse of `YAMLWriter`, with loose/strict modes) |
+| `BindingLoadError` | Exception raised when binding parsing fails; carries `file_path`, `module_id`, `missing_fields`, `reason` |
 | `PythonWriter` | Generates `@module`-decorated Python wrapper files |
 | `RegistryWriter` | Registers modules directly into an `apcore.Registry` |
 | `HTTPProxyRegistryWriter` | Registers HTTP proxy modules that forward requests to a running API |
@@ -246,12 +251,6 @@ def deploy(env: str, tag: str = "latest") -> dict:
 
 Input and output schemas are inferred from PEP 484 type annotations. Use `include` / `exclude` regex filters to control which module IDs are registered.
 
-## Requirements
-
-- Python >= 3.11
-- apcore >= 0.14.0
-- pydantic >= 2.0
-- PyYAML >= 6.0
 
 ## Documentation
 

{apcore_toolkit-0.4.2 → apcore_toolkit-0.6.0}/README.md

@@ -22,6 +22,8 @@ pip install apcore-toolkit
 | `ScannedModule` | Canonical dataclass representing a scanned endpoint |
 | `BaseScanner` | Abstract base class for framework scanners with filtering and deduplication |
 | `YAMLWriter` | Generates `.binding.yaml` files for `apcore.BindingLoader` |
+| `BindingLoader` | Parses `.binding.yaml` files back into `ScannedModule` objects (pure-data inverse of `YAMLWriter`, with loose/strict modes) |
+| `BindingLoadError` | Exception raised when binding parsing fails; carries `file_path`, `module_id`, `missing_fields`, `reason` |
 | `PythonWriter` | Generates `@module`-decorated Python wrapper files |
 | `RegistryWriter` | Registers modules directly into an `apcore.Registry` |
 | `HTTPProxyRegistryWriter` | Registers HTTP proxy modules that forward requests to a running API |
@@ -220,12 +222,6 @@ def deploy(env: str, tag: str = "latest") -> dict:
 
 Input and output schemas are inferred from PEP 484 type annotations. Use `include` / `exclude` regex filters to control which module IDs are registered.
 
-## Requirements
-
-- Python >= 3.11
-- apcore >= 0.14.0
-- pydantic >= 2.0
-- PyYAML >= 6.0
 
 ## Documentation
 

{apcore_toolkit-0.4.2 → apcore_toolkit-0.6.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "apcore-toolkit"
-version = "0.4.2"
+version = "0.6.0"
 description = "Shared scanner, schema extraction, and output toolkit for apcore framework adapters"
 requires-python = ">=3.11"
 readme = "README.md"
@@ -23,17 +23,18 @@ keywords = [
     "toolkit",
 ]
 dependencies = [
-    "apcore>=0.18.0",
+    "apcore>=0.21.0",
     "pydantic>=2.0",
     "PyYAML>=6.0",
 ]
 
 [project.optional-dependencies]
 http-proxy = ["httpx>=0.24"]
+json-schema = ["jsonschema>=4.0"]
 dev = [
-    "pytest>=7.0",
+    "pytest>=8.0",
     "pytest-cov>=4.0",
-    "ruff>=0.1",
+    "ruff>=0.9",
     "mypy>=1.0",
     "apdev[dev]>=0.2.1",
     "httpx>=0.24",

{apcore_toolkit-0.4.2 → apcore_toolkit-0.6.0}/src/apcore_toolkit/__init__.py

@@ -6,8 +6,14 @@ Public API re-exports for convenient access to core types and utilities.
 from importlib.metadata import PackageNotFoundError
 from importlib.metadata import version as _get_version
 from apcore_toolkit.ai_enhancer import AIEnhancer, Enhancer
+from apcore_toolkit.binding_loader import BindingLoader, BindingLoadError
 from apcore_toolkit.display import DisplayResolver
-from apcore_toolkit.formatting import to_markdown
+from apcore_toolkit.formatting import (
+    format_module,
+    format_modules,
+    format_schema,
+    to_markdown,
+)
 from apcore_toolkit.openapi import (
     deep_resolve_refs,
     extract_input_schema,
@@ -16,7 +22,7 @@ from apcore_toolkit.openapi import (
     resolve_schema,
 )
 from apcore_toolkit.output import get_writer
-from apcore_toolkit.output.errors import WriteError
+from apcore_toolkit.output.errors import InvalidFormatError, WriteError
 from apcore_toolkit.output.python_writer import PythonWriter
 from apcore_toolkit.output.http_proxy_writer import HTTPProxyRegistryWriter
 from apcore_toolkit.output.registry_writer import RegistryWriter
@@ -32,10 +38,23 @@ from apcore_toolkit.output.verifiers import (
 from apcore_toolkit.output.yaml_writer import YAMLWriter
 from apcore_toolkit.pydantic_utils import flatten_pydantic_params, resolve_target
 from apcore_toolkit.convention_scanner import ConventionScanner
-from apcore_toolkit.scanner import BaseScanner
+from apcore_toolkit.http_verb_map import (
+    SCANNER_VERB_MAP,
+    extract_path_param_names,
+    generate_suggested_alias,
+    has_path_params,
+    resolve_http_verb,
+    substitute_path_params,
+)
+from apcore_toolkit.scanner import (
+    BaseScanner,
+    deduplicate_ids,
+    filter_modules,
+    infer_annotations_from_method,
+)
 from apcore_toolkit.schema_utils import enrich_schema_descriptions
 from apcore_toolkit.serializers import annotations_to_dict, module_to_dict, modules_to_dicts
-from apcore_toolkit.types import ScannedModule
+from apcore_toolkit.types import ScannedModule, clone_module, create_scanned_module
 
 try:
     __version__ = _get_version("apcore-toolkit")
@@ -44,16 +63,20 @@ except PackageNotFoundError:
 
 __all__ = [
     "AIEnhancer",
+    "BindingLoadError",
+    "BindingLoader",
     "DisplayResolver",
     "BaseScanner",
     "ConventionScanner",
     "HTTPProxyRegistryWriter",
     "Enhancer",
+    "InvalidFormatError",
     "JSONVerifier",
     "MagicBytesVerifier",
     "PythonWriter",
     "RegistryVerifier",
     "RegistryWriter",
+    "SCANNER_VERB_MAP",
     "ScannedModule",
     "SyntaxVerifier",
     "Verifier",
@@ -63,17 +86,30 @@ __all__ = [
     "YAMLVerifier",
     "YAMLWriter",
     "annotations_to_dict",
+    "clone_module",
+    "create_scanned_module",
+    "deduplicate_ids",
     "deep_resolve_refs",
     "enrich_schema_descriptions",
     "extract_input_schema",
     "extract_output_schema",
+    "extract_path_param_names",
+    "filter_modules",
     "flatten_pydantic_params",
+    "format_module",
+    "format_modules",
+    "format_schema",
+    "generate_suggested_alias",
     "get_writer",
+    "has_path_params",
+    "infer_annotations_from_method",
     "module_to_dict",
     "modules_to_dicts",
+    "resolve_http_verb",
     "resolve_ref",
     "resolve_schema",
     "resolve_target",
     "run_verifier_chain",
+    "substitute_path_params",
     "to_markdown",
 ]

apcore_toolkit-0.6.0/src/apcore_toolkit/_type_mapping.py

@@ -0,0 +1,19 @@
+"""Shared Python ↔ JSON Schema type vocabulary.
+
+Single source of truth for the 6-type mapping used by ConventionScanner
+(Python→JSON Schema) and PythonWriter (JSON Schema→Python). Adding a new
+type here propagates to both automatically.
+"""
+
+from __future__ import annotations
+
+PYTHON_TO_JSON_SCHEMA: dict[str, str] = {
+    "str": "string",
+    "int": "integer",
+    "float": "number",
+    "bool": "boolean",
+    "list": "array",
+    "dict": "object",
+}
+
+JSON_SCHEMA_TO_PYTHON: dict[str, str] = {v: k for k, v in PYTHON_TO_JSON_SCHEMA.items()}