Maintenance release. Documentation only.
Why this release exists
The README published with 0.1.0 stated that the package was not yet on npm and
presented the real install commands as hypothetical. npm renders a package page
from the README inside the published tarball, so that text remained on the
package page after 0.1.0 was published. Replacing it required publishing a
further version.
What changed
- The README states the published state and leads with the real install
commands; the clone is kept as the from-source alternative. - The first line names the Agent Manifest command-line interface (CLI), binding
the acronym to its expansion. - Added links to the canonical documentation page
(https://agent-manifest-spec.org/docs/cli/), the npm package page, and the
project's contact path.
What did not change
No change to the command contract, the arguments, the exit codes, the --json
shape, the vendored Agent Manifest v1.0 schema, or any dependency. No new
commands and no new capabilities. A manifest that validated under 0.1.0
validates identically under 0.1.1. The Agent Manifest specification is
unaffected: a CLI release never implies a specification release.
Verification
| Tag | v0.1.1 → 8b3501d002b8b70e02c4048a22e04b82145b1b41 |
| Tarball sha-256 | 5a9f91381d8b90ba8621272f1833bf2fbd7e1010318260b9329e1a21f81fc6ab |
| Vendored schema sha-256 | c1e3caaf9543f2a5d610ccdfaf36329562fe03b6db00c4ea30b7ef0b7b8ef70a |
| Contents | 15 files, 58 841 B unpacked |
| Integrity | sha512-R+Vgnb8KhWMSYfm6lAllINS1bpwci0B7D3nKL07dyaCpbteOVKwFvcENlQjt/3aiW0UjOJe2wAMoE5LtTJJSww== |
This is the first release published through GitHub Actions with npm trusted
publishing (OIDC), and the first to carry provenance. The provenance statement
attests the repository, the workflow file .github/workflows/release.yml, the
ref refs/tags/v0.1.1 and the commit above, and is recorded in the Sigstore
transparency log. 0.1.0 was published by hand and has no attestation; that
remains the case and is stated on the documentation page.
The tool validates the structure of a declaration against the published schema.
It does not certify, score, rank, attest to behaviour, or enforce anything at
runtime, and a manifest that validates is a well-formed declaration, not
evidence that the declaring agent behaves as declared.
Known issue
The Status table in this release's README still records the version as 0.1.0.
The package, the CHANGELOG and agent-manifest --version all correctly report
0.1.1. This will be corrected in the next release.