aibdd-form-api-spec

To generate OpenAPI 3.x YAML contracts, you provide an inference package and a Planner-provided slice list to produce modular YAML files with standardized error schemas in your target contracts directory.

Boundary-aware planning maps each inferred endpoint to an exact REST path and HTTP method while preserving boundary-scope ownership, ensuring no cross-boundary decisions are made during the API contract generation.

You can split a large OpenAPI specification by using a Planner-provided slice list to generate per-slice YAML files that utilize correct cross-file $ref links and shared common.yml schema patterns.

If the target_path violates the flat directory constraint, the generation fails fast and prompts the Planner for repair, enforcing strict target_path assertions to maintain contract correctness.

You need a Planner to provide the slice list for splitting outputs, while the generation process automatically standardizes ErrorResponse usage via common.yml to align error schemas across files.

Generation fails on incomplete input because the tool enforces target_path assertions and requires a complete Planner-provided slice list, falling back to the Planner for repair when input is incomplete.