@archpilotlabs/archpilot 0.2.6 → 0.2.8

package/CHANGELOG.md

@@ -1,5 +1,59 @@
 # Changelog
 
+## 0.2.8
+
+### Added
+
+- Added architecture review state for repositories that evolve after initial setup.
+- Added detection for newly discovered high-confidence architecture modules after Smart Init.
+- Added explicit architecture model evolution support so new modules can be reviewed, marked Not Now, or accepted into the governed architecture model.
+- Added effective analysis for high-confidence observed modules before they are accepted into `.archpilot/architecture.json`.
+- Added AP-ARCH-012 guidance for module review state, including newly discovered, previously reviewed/not governed, governed, and declared-missing modules.
+
+### Improved
+
+- Improved dependency graph and module ownership analysis so newly observed modules participate in applicable architecture validation before acceptance.
+- Improved AP-APP, AP-DQR, AP-TXN/AP-DOM, AP-AUTH/AP-TEN, and AP-API analysis for high-confidence observed modules where canonical rule semantics support module attribution.
+- Improved architecture model review so acceptance uses the canonical model apply flow and Validate never silently rewrites `.archpilot/architecture.json`.
+- Improved declared-missing module handling so governed modules that are no longer observed are surfaced for explicit review.
+
+### Notes
+
+- `architecture.json` remains the governed architecture model; `.archpilot/architecture-review-state.json` stores review memory for previously seen but not governed modules.
+- Review status does not suppress validation. Actual AP-\* violations inside observed modules affect Architecture Health normally.
+- New-module review guidance itself does not directly reduce Architecture Health.
+- Contracts remain governed-only and are not fabricated for observed modules.
+
+---
+
+## 0.2.7
+
+### Added
+
+- Added `archpilot validate --regressions` to focus validation output on architecture findings introduced since the accepted governance baseline.
+- Added regression summaries showing introduced, resolved, and existing architecture findings.
+- Added regression comparison data to JSON validation output for automation and tooling.
+- Added automatic initial governance baseline creation after the first successful full local validation, so regression tracking works without additional setup.
+
+### Improved
+
+- Improved CI and pull request reporting to highlight newly introduced architecture regressions instead of presenting existing architecture debt as newly actionable.
+- Improved GitHub inline annotations to prioritize newly introduced supported findings when a governance baseline is available.
+- Improved regression reporting with separate visibility for resolved findings and existing baseline findings.
+- Improved missing-baseline guidance to clearly distinguish the governance baseline from the structural architecture baseline.
+- Scoped `--changed` and `--diff` validation now avoids unsafe full-baseline comparisons that could incorrectly report findings as resolved.
+
+### Notes
+
+- Regression comparison uses the accepted governance baseline at `.archpilot/baseline/baseline.json`.
+- The initial governance baseline is created automatically only after a successful full local validation. Existing baselines are never automatically refreshed.
+- Use `archpilot baseline refresh` when you intentionally want to accept the current architecture findings as the new governance baseline.
+- `--regressions` does not change Architecture Health Score, Setup Readiness Score, rule severities, scoring, or normal validation findings.
+- `--regressions` does not currently combine with `--changed` or `--diff`.
+- Regression reporting does not independently change CI exit or policy enforcement behavior.
+
+---
+
 ## 0.2.6
 
 ### Improved

package/README.md

@@ -45,7 +45,9 @@ ArchPilot turns architecture into something you can actually run and verify:
 - Generate architecture scores and reports
 - Surface architecture feedback in local development, PRs, and CI
 
-No runtime agents. No external services. Fully deterministic and local-first.
+As repositories evolve, ArchPilot distinguishes governed architecture from high-confidence modules observed in the current source tree. Newly discovered modules are analyzed before governance acceptance, while adding them to `.archpilot/architecture.json` remains an explicit architecture review decision.
+
+**No cloud scan required. Deterministic and local-first.**
 
 ArchPilot works alongside GitHub Copilot, Claude Code, Codex, Cursor, and other AI coding tools by continuously validating architectural boundaries before architectural drift becomes technical debt.
 
@@ -172,6 +174,22 @@ Creates `.archpilot/` with architecture config, rules, and baseline artifacts.
 archpilot validate
 ```
 
+To focus on architecture changes introduced since the governance baseline:
+
+```bash
+archpilot validate --regressions
+```
+
+ArchPilot automatically creates the initial governance baseline after the first successful full local validation. Regression validation can then distinguish newly introduced, existing, and resolved architecture findings.
+
+When you intentionally accept the current architecture findings as the new reference, run:
+
+```bash
+archpilot baseline refresh
+```
+
+The governance baseline used for regression comparison is separate from the structural baseline used by `archpilot baseline create`.
+
 Example output:
 
 ```text
@@ -317,6 +335,5 @@ Proprietary. See LICENSE file for details.
 
 - Website: https://archpilot.org
 - Documentation: https://archpilot.org/docs
-- [Changelog](https://github.com/archpilotlabs/archpilot-vscode/blob/main/packages/cli/CHANGELOG.md)
 
 ---