empirical-sdd 0.26.1 → 0.28.0

package/CHANGELOG.md

@@ -8,6 +8,49 @@ under the alpha rules in [docs/versioning.md](docs/versioning.md).
 
 ## [Unreleased]
 
+## [0.28.0] - 2026-08-24
+
+### Added
+
+- Added a deterministic specialist-consult protocol with bounded security and
+  UI/UX packets, structured advisory evidence, and domain-scoped blocking
+  without standing roles or persisted model reasoning.
+- Added structured repository-activation inspection and Doctor findings for
+  missing, stale, malformed, unsafe, non-canonical, nested-shadowing, and
+  same-name global skill states, with exact per-runtime verification and reload
+  guidance.
+- Added the native Windsurf workspace skill, nested-directory resolution, root
+  Codex override reconciliation, and linked-worktree isolation coverage.
+
+### Fixed
+
+- Front-loaded mutation trigger metadata and marker-owned instructions so
+  bounded host context cannot omit Empirical behind large user content, while
+  preserving user-owned bytes and keeping read-only work outside the workflow.
+- Stopped treating current integration files as proof that an already-running
+  agent loaded them; reports now keep runtime loading explicitly unverified.
+
+### Migration
+
+- Existing Schema 5 and Tracker Policy v1/v2 repositories require no state
+  migration. Run Empirical Init once in existing repositories to reconcile the
+  expanded activation artifacts, then follow Doctor's runtime reload guidance.
+
+## [0.27.0] - 2026-08-21
+
+### Changed
+
+- Made Tracker Policy v2 lifecycle comments human-first across GitHub, Linear,
+  and Jira, with plain-language status, focused action requests, friendly
+  evidence links, native Jira formatting, and provider-safe exact recovery
+  markers that remain compatible with existing comments.
+
+### Migration
+
+- Existing Schema 5 and Tracker Policy v1/v2 repositories require no state
+  migration. Visibility cadence, ticket bindings, issue descriptions, and
+  historical comments remain compatible.
+
 ## [0.26.1] - 2026-08-21
 
 ### Fixed
@@ -193,7 +236,9 @@ Published through GitHub Actions trusted publishing with npm provenance.
 
 - Prepared and released package version `0.20.2`.
 
-[Unreleased]: https://github.com/goempirical/empirical-sdd/compare/v0.26.1...HEAD
+[Unreleased]: https://github.com/goempirical/empirical-sdd/compare/v0.28.0...HEAD
+[0.28.0]: https://github.com/goempirical/empirical-sdd/compare/v0.27.0...v0.28.0
+[0.27.0]: https://github.com/goempirical/empirical-sdd/compare/v0.26.1...v0.27.0
 [0.26.1]: https://github.com/goempirical/empirical-sdd/compare/v0.26.0...v0.26.1
 [0.26.0]: https://github.com/goempirical/empirical-sdd/compare/v0.25.0...v0.26.0
 [0.25.0]: https://github.com/goempirical/empirical-sdd/compare/v0.24.1...v0.25.0

package/README.md

@@ -4,7 +4,7 @@ Agent-neutral, resumable spec-driven development for coding agents. Empirical
 turns an ordinary change request into a deterministic workflow with durable
 state, reviewable evidence, and safe Git integration.
 
-> Empirical 0.26 is alpha software. It requires Node.js 22 or newer.
+> Empirical 0.28 is alpha software. It requires Node.js 22 or newer.
 
 ## Install
 
@@ -23,9 +23,13 @@ uses `@empirical-init`. Existing 0.22 repositories should invoke it once after
 upgrading; configuration, history, and evidence are preserved.
 
 Doctor verifies that completed repositories still have every required local
-instruction, skill, and MCP bridge. If it reports missing or drifted project
-integrations, invoke `empirical-init` explicitly to reconcile Empirical-owned
-artifacts; unmanaged or unsafe conflicts are preserved and remain visible.
+instruction, native skill, and MCP bridge, including nested-directory and
+linked-worktree discovery. It distinguishes missing, stale, malformed, unsafe,
+non-canonical, shadowing, and global-collision states. Invoke `empirical-init`
+explicitly to reconcile Empirical-owned artifacts; unmanaged or unsafe
+conflicts are preserved. Correct files do not prove that an existing host
+session loaded them, so Doctor reports runtime loading as unverified and gives
+the applicable reload or fresh-session step.
 
 ## What it provides