Spectra 3.1.3

Persistent, governed project intelligence for coding agents. 3.1.3 adds Project Intelligence queries and scoped verification evidence, and separates the machine lifecycle from the project lifecycle.

No breaking changes. No project migration is required. schemaVersion stays 3, apiVersion stays spectra/v2, and no command or flag is removed.

Upgrade notes

Native 3.1.2 users: 3.1.2 predates the managed-install ownership record and cannot be replaced in place by its old spectra update path. Install 3.1.3 into a fresh managed location with the current installer (it prints the exact commands). Your project files are not modified and no project migration is required.

• Global npm: npm install -g spectra-pack@latest
• npx: npx spectra-pack@latest ...
• Existing projects: refresh generated files and agent guidance with spectra doctor --fix, then spectra adapters --agents <csv>. Handwritten AGENTS.md and CLAUDE.md files are protected unless you pass --force.
• From 3.1.3 on, a managed native install records ownership, so spectra update can update it.

Highlights

Project Intelligence

• spectra inspect <id> explains what governs a rule, requirement, scenario, invariant, module or test target, and whether it is verified.
• spectra inspect --changed, --base <ref> and --file <path> report the impact of changed files at module and canonical-source level. This is not a code graph.

Verification and gates

• spectra verify --test-target <id> records scoped, local verification evidence. Subjects report verified, failed, stale or unverified.
• spectra verify --explain <id> says why. spectra verify --gate review|release reports whether the evidence lets a stage proceed.
• Evidence is scoped: a passing test target supports the subjects that declare it. It does not prove a requirement everywhere.

Context and retrieval

• spectra context --route-task selects exact knowledge objects within the role budget, now also matches architectural invariants, and folds plural and -ing/-ed variants.
• Retrieval stays deterministic, lexical and budget-aware. There is no semantic or vector search.

Lifecycle

• spectra update changes the machine application only. It never reads or writes a project.
• spectra migrate is the explicit per-project step. spectra uninstall removes the native application and leaves every project unchanged.
• Derived caches rebuild on their own and never need a migration.

Agent guidance

• Generated adapters cover route-first context, business memory, Project Intelligence commands and the verification gates.
• Agent-facing JSON carries contractVersion 1 and structured errors. context and route JSON no longer include absolute paths.

Fixes

• Adapters generated in new projects no longer omit the route-first and business-memory guidance.
• spectra verify --test-target finds locally installed tools in the package's node_modules/.bin.
• spectra knowledge promote|supersede|deprecate no longer matches a rule whose ID only starts with the requested ID.
• spectra verify --gate refuses an unresolvable --base/--head ref.

Documentation

README, CLI reference and website describe all 24 commands and the three lifecycles. The website diagrams are cleaner.

Full details: CHANGELOG.

v3.1.2

Improves adoption discovery, project documentation ownership and the command-effect guides following 3.1.1. The spectra/v2 schema identifier and installation schema version 3 remain unchanged.

• Adoption projects repository evidence into discovery documents without running application commands or treating technical findings as confirmed business intent.
• Compatible plugin and skill documents are directed by generated agent guidance to .spectra/docs/<project-name>/<plugin-or-skill>/; tool-required paths remain supported. Install metadata keeps the project documentation name stable across later brief changes.
• Runtime refresh preserves user memory, plugin documents and unowned guide collisions. Explicit adapter generation follows the target project's ownership policy.
• Refreshing through the project-local npm launcher preserves its own CLI and runtime files, keeping doctor --fix and repeated installation usable.
• All 21 public commands have documented file effects, and the website diagrams match the site's typography and cards while retaining complete explanations.
• After updating an existing project, regenerate its agent instructions with spectra adapters --agents <csv> to receive the new output guidance. Existing plugin documents are not automatically moved.

Spectra 3.1.1

Spectra 3.1.1 is a correctness release. The public spectra/v2 schema identifier is unchanged.

Highlights

• Uses one unified installation without Lite/Full profile selection; project state stays under .spectra/.
• Makes spectra verify release-grade by default and blocks release approval while any nested checklist item is incomplete.
• Persists release approvals across invocations, invalidates them when relevant semantic scope changes, and rejects approval while project changes are uncommitted.
• Fixes repeated spectra context calls and generated agent adapter paths.
• Updates the direct yaml dependency to 2.9.1.

Native downloads

macOS and Linux binaries are attached below for x64 and arm64. Each archive includes a SHA-256 checksum file.

For setup and migration instructions, see the README.

v3.1.0

Spectra native binaries for v3.1.0

v3.0.9

Spectra native binaries for v3.0.9

v3.0.8

Spectra 3.0.8 patch release.\n\nHighlights:\n- Aligns the public CLI reference and generated profile docs with the current command surface.\n- Documents Full-only agent adapter generation via --agents.\n- Exposes spectra help verify and fixes spectra check --help usage text.\n- Bumps packaged runtime, templates, native install docs, and manifests to 3.0.8.\n\nVerification:\n- npm test --workspaces --if-present\n- npm pack --workspace packages/cli --dry-run\n- PR #8 checks passed.

v3.0.7

Spectra native binaries for v3.0.7

v3.0.6

Spectra native binaries for v3.0.6

v3.0.5

Spectra native binaries for v3.0.5

v3.0.4

Spectra native binaries for v3.0.4