Publish v2 API and module manifest - #254
Merged
Merged
Conversation
This was referenced Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #225
What changed
base_api_manifest.yaml, a versioned v2.0.0 API/module manifest covering the namespace contract, modules, dependencies, Bash minimum, symbols, API metadata, environment/globals, optional commands, documentation, tests, and artifact membership.scripts/api-manifestchecker/generator. It validates missing and duplicate symbols, source drift, unsafe paths, dependency cycles, packaging membership, metadata, and stale generated documentation, and exposes manifest-driven source/test/artifact paths.docs/api-reference.mdand the schema/consumer guide atdocs/api-manifest-schema.md.tests/validate.shto discover module source files, BATS suites, ShellCheck targets, and artifacts from the API manifest rather than a second hardcoded module inventory.STANDARDS.mdand the changelog to use the finalizedbase_public namespace.Design notes
base_manifest.yamlremains the Base release/developer-tooling manifest. The APImanifest is separate so Base's existing manifest schema is not extended with
library-specific fields. The API manifest uses a documented line-oriented YAML
subset and has no mandatory Python, Ruby,
yq, orjqruntime for consumers.Validation
./tests/validate.sh </dev/nulltests/lint-warnings.shreports only the repository's existing warning baselinegit diff --checkpassed