v1.1.1

1.1.1 (2026-06-26)

Bug Fixes

• add memory fragment type and gracefully format validation errors (d06103f), closes #3 #4

v1.1.0

1.1.0 (2026-06-26)

Features

• add build --check to verify vendor files are in sync (275fe1b)

v1.0.0

First stable release: the CLI surface, MCP tool surface, and manifest schema are
now stable and versioned under SemVer. Cut as a major because the vendor-file
output format changed (see Changed).

Added

• pack --budget <n> to override the manifest token budget per run, and
  pack --exact to count tokens with the bundled gpt-tokenizer (cl100k)
  instead of the chars/4 estimate.
• lint now warns about fragments whose content alone exceeds the budget
  (they can never be packed).
• build --target <name...> to compile only selected vendors
  (claude, gemini, agents, cursor).
• agenticscope schema — generate schema/manifest.schema.json from the zod
  schema for TOML editor autocomplete/validation.
• agenticscope mcp-config — print ready-to-paste MCP server config per host
  (Claude Desktop, Cursor, generic).
• MCP server HTTP transport: agenticscope-mcp --http [port] serves over
  Streamable HTTP for remote/hosted use, alongside the default stdio transport.

Changed

• BREAKING: vendor files are now rendered per vendor. CLAUDE.md/GEMINI.md/
  AGENTS.md get vendor-specific markdown preambles and .cursorrules is a plain
  instruction file (no markdown H1). The old single # Agent context for <name>
  header is gone. Re-run agenticscope build to regenerate.

Security

• MCP project arguments are scope-guarded to the workspace root; paths that
  escape it (../…, absolute paths outside) are rejected.

v0.2.1

0.2.1 (2026-06-24)

Bug Fixes

• correct repository.url and auto-publish from main via OIDC trusted publishing (537ec9e)
• correct repository.url and auto-publish from main via OIDC trusted publishing (dcf50b8)
• correct repository.url and auto-publish from main via semantic-release (4060980)
• drop setup-node registry-url so npm uses OIDC trusted publishing (7bbdda5)
• publish via top-level OIDC step instead of semantic-release exec (9b3e34f)
• run release without environment so OIDC subject matches trusted publisher (d4434f7)
• strip setup-node token placeholder from npmrc so npm uses OIDC (90e8f07)
• use node 24 so npm 11 enables OIDC trusted publishing (0098366)