Repository navigation
v1.0.0
[1.0.0] - 2026-05-26
The 1.0 line. Stability promise applies from this release onward (see README
Stability section): CLI flag surface, manifest schema, lockfile shape, and
exit codes are the public API.
Changed
- BREAKING:
--strict-sha256is now the default.forgent addagainst
a registry whose manifest omits per-filesha256now errors (exit 1)
instead of warning. Pass--no-strict-sha256(new flag) or set
FORGENT_STRICT_SHA256=0to restore 0.x behaviour during migration.
The existing--strict-sha256flag andFORGENT_STRICT_SHA256=1env
var still work as explicit opt-ins (now no-ops matching the default).
Rationale: this was the planned 1.0 behaviour. The 0.x soft default
existed as a migration window for third-party registries to add hashes. resolveRegistryBaseis nowasync. Internal API change — does not
affect CLI users. Programmatic importers shouldawaitthe call.
Added
-
forgent registrysubcommand for multi-registry workflows:registry list— print configured registries (*marks default).registry add <name> <url-or-path> [--default] [--force]— persist
a named registry inforgent.config.json. Name validated via
assertSafeName(kebab-case).registry remove <name>— drop one; clearsdefaultRegistryif it
was the default.registry set-default <name>— switch the default.
Resolution order for the active registry is now:
--registry <value>(name match in config, else literal url/path).FORGENT_REGISTRYenv (same name-or-literal interpretation).forgent.config.jsondefaultRegistry(by name).- Built-in default URL.
forgent.config.jsongains optionalregistries[]+defaultRegistry
fields. Existing configs without these fields keep working (treated as
zero configured registries). -
forgent hash-files [--registry <path>]— walk everyitems[].files[]
entry, compute sha256, diff against the manifest-declared hash. Prints
per-filematch/MISMATCH/MISSING — add to manifest, plus a summary.
Exits 1 on any mismatch or missing-from-manifest. Local-registry only —
HTTP URLs are rejected. For third-party registry authors keeping their
manifest in sync. -
forgent validate-skill <name>— read everyskill:exampleJSON file
declared by<name>, follow its$schemaURL, and validate the example
against that schema. Built-in hand-rolled validator covers the keywords
emitted byagent-skill/schema/subagent-output.schema.json:type,
required,properties,additionalProperties: false,enum,pattern,
minLength,minimum,items(single subschema), local$ref
(#/$defs/...). Unsupported keywords (maxLength,oneOf,allOf, …)
emit a single WARN per keyword then skip the constraint. Exits 1 on FAIL. -
Stability promise documented in README §Stability. forgent ≥ 1.0
follows semver. Internalsrc/*.jsmodules are not public — pin to a
major if you import them programmatically. The default registry URL is
stable but may move to a CDN domain post-1.0 without a major bump.