v0.3.1

v0.3.1

Changes

@tanstack/intent

0.3.1

Patch Changes

• #176 5419b02 - Add agent-safe hidden skill source handling to intent list.

  intent list now detects agent sessions with std-env and redacts unlisted allowlist candidates from agent-facing output. Agents see allowed skills plus a count-only hidden-source notice, while intent list --show-hidden reveals hidden source names only outside agent sessions.

  Agent-mode JSON output includes hiddenSourceCount but leaves hiddenSources empty, preventing structured output from leaking package names that could be added to package.json#intent.skills.

Packages

• @tanstack/intent@0.3.1

v0.3.0

v0.3.0

Changes

@tanstack/intent

0.3.0

Minor Changes

• #174 089a355 - Add intent hooks install for supported AI coding agents.

  This adds lifecycle-hook installation for supported agents, including project/user scope handling, generated hook runner scripts, and agent-specific enforcement policy. It also documents the hook setup flow and adds eval/test coverage for hooked intent discovery.

Packages

• @tanstack/intent@0.3.0

@tanstack/intent@0.3.1

Patch Changes

• #176 5419b02 - Add agent-safe hidden skill source handling to intent list.

  intent list now detects agent sessions with std-env and redacts unlisted allowlist candidates from agent-facing output. Agents see allowed skills plus a count-only hidden-source notice, while intent list --show-hidden reveals hidden source names only outside agent sessions.

  Agent-mode JSON output includes hiddenSourceCount but leaves hiddenSources empty, preventing structured output from leaking package names that could be added to package.json#intent.skills.

@tanstack/intent@0.3.0

Minor Changes

• #174 089a355 - Add intent hooks install for supported AI coding agents.

  This adds lifecycle-hook installation for supported agents, including project/user scope handling, generated hook runner scripts, and agent-specific enforcement policy. It also documents the hook setup flow and adds eval/test coverage for hooked intent discovery.

v0.2.1

v0.2.1

Changes

@tanstack/intent

0.2.1

Patch Changes

• #171 392016b - Adds package source-kind metadata to scanner results, tightens scan stats to match the runtime contract, and adds focused markdown destination rewrite coverage while preserving the current name-based allowlist behavior.

Packages

• @tanstack/intent@0.2.1

v0.2.0

v0.2.0

Changes

@tanstack/intent

0.2.0

Minor Changes

• #169 0dbf9d0 - Add intent validate --check and intent validate --fix for mechanical SKILL.md frontmatter migrations.

  --check reports pending migrations without writing files. --fix rewrites fixable name and metadata scalar migrations, then re-runs validation.

Patch Changes

• #168 9eee8a5 - Make SKILL.md frontmatter spec-compliant. name must now be a spec-legal leaf segment matching its parent directory (lowercase letters, numbers, and hyphens; 64 characters max; no slashes), and the Intent-specific scalars type, library, library_version, and framework live under the metadata map. intent validate now errors on a slash/non-leaf name, a name with non-spec characters or over 64 characters, non-spec top-level scalar keys, and a non-string metadata map. Skill identity is derived from the directory path rather than the frontmatter name, and the generate-skill and tree-generator templates emit the new shape.

Packages

• @tanstack/intent@0.2.0

@tanstack/intent@0.2.1

Patch Changes

• #171 392016b - Adds package source-kind metadata to scanner results, tightens scan stats to match the runtime contract, and adds focused markdown destination rewrite coverage while preserving the current name-based allowlist behavior.

@tanstack/intent@0.2.0

Minor Changes

• #169 0dbf9d0 - Add intent validate --check and intent validate --fix for mechanical SKILL.md frontmatter migrations.

  --check reports pending migrations without writing files. --fix rewrites fixable name and metadata scalar migrations, then re-runs validation.

Patch Changes

• #168 9eee8a5 - Make SKILL.md frontmatter spec-compliant. name must now be a spec-legal leaf segment matching its parent directory (lowercase letters, numbers, and hyphens; 64 characters max; no slashes), and the Intent-specific scalars type, library, library_version, and framework live under the metadata map. intent validate now errors on a slash/non-leaf name, a name with non-spec characters or over 64 characters, non-spec top-level scalar keys, and a non-string metadata map. Skill identity is derived from the directory path rather than the frontmatter name, and the generate-skill and tree-generator templates emit the new shape.

v0.1.1

v0.1.1

Changes

@tanstack/intent

0.1.1

Patch Changes

• #165 2676302 - Remove the unused feedback APIs, bundled feedback meta-skill, tests, and docs references.

• #162 d5d9181 - Read skill frontmatter scalar fields (type, framework, library_version)
  from metadata.* with a fallback to the top-level key (#159). This is a
  back-compat safety net for the frontmatter migration: skills authored in the
  new metadata-nested shape resolve correctly while existing top-level skills
  keep working unchanged. The scanner, staleness checker, and the framework
  requires validation all honor both shapes.

Packages

• @tanstack/intent@0.1.1

@tanstack/intent@0.1.1

Patch Changes

• #165 2676302 - Remove the unused feedback APIs, bundled feedback meta-skill, tests, and docs references.

• #162 d5d9181 - Read skill frontmatter scalar fields (type, framework, library_version)
  from metadata.* with a fallback to the top-level key (#159). This is a
  back-compat safety net for the frontmatter migration: skills authored in the
  new metadata-nested shape resolve correctly while existing top-level skills
  keep working unchanged. The scanner, staleness checker, and the framework
  requires validation all honor both shapes.