delivery-friction-analyzer 0.13.0 → 0.14.1

package/README.md

@@ -144,6 +144,8 @@ No separate model-ready context artifact is required for this workflow. Reconsid
 
 ## Development Notes
 
+Repo-local maintainer and agent review expectations live in [AGENTS.md](AGENTS.md).
+
 ### Current Direction
 
 Delivery Friction Analyzer is currently a local, GitHub-connected analyzer that produces repository-level friction reports from live pull request data. It is repo-source-agnostic: repository-specific assumptions live in profiles.

package/docs/reference/release-automation.md

@@ -28,6 +28,12 @@ It validates:
 
 CI runs on Node 20 and Node 24 so the advertised `engines.node >=20` floor is exercised before release.
 
+## Local Preflight
+
+For ordinary PRs, run `npm run preflight` before opening or updating review. It runs the full local test suite and `git diff --check HEAD` so whitespace issues are caught across staged and unstaged tracked changes.
+
+For release automation, package metadata, package contents, or publish workflow changes, run `npm run preflight:release`. It runs the focused release-versioning tests, including direct CLI entrypoint coverage, validates the package version is not behind the latest local `v*` release tag, and runs `npm pack --dry-run`.
+
 ## Release Workflow
 
 The release workflow runs on pushes to `main` and skips commits whose subject starts with `Release `.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "delivery-friction-analyzer",
-  "version": "0.13.0",
+  "version": "0.14.1",
   "description": "Local GitHub pull request analytics for delivery friction reports.",
   "license": "MIT",
   "type": "module",
@@ -19,6 +19,8 @@
   ],
   "scripts": {
     "analyze:github": "node src/cli/analyze-github.js",
+    "preflight": "npm test && git diff --check HEAD",
+    "preflight:release": "node --test test/release-versioning.test.mjs && node scripts/release-versioning.mjs assert-package-not-behind-latest-tag && npm pack --dry-run",
     "report:fixture": "node src/report/generate-report.js --metrics-summary fixtures/github/mcp-writing/metrics-summary.golden.json --json-out fixtures/github/mcp-writing/reports/friction-report.golden.json --markdown-out fixtures/github/mcp-writing/reports/friction-report.golden.md",
     "test": "node --test"
   },

package/release-log.md

@@ -2,6 +2,22 @@
 
 ## Unreleased
 
+### 2026-06-21 — Repo-Specific Review Guidance
+
+- What changed: Added repo-local maintainer and agent guidance for recurring review themes, broad-change tripwires, and validation command selection, with self-profile coverage for the new guidance file.
+- Why it matters: Maintainers and agents can catch known review-readiness issues before opening PRs without applying heavy process to tiny docs or test changes, and future self-analysis can classify the guidance surface.
+- Who is affected: Maintainers and agents preparing changes in this repository.
+- Action needed: Optional; review `AGENTS.md` before broad, report/contract, profile, docs, or release/package changes.
+- PR: #52
+
+### 2026-06-21 — Local Preflight Commands
+
+- What changed: Added `npm run preflight` for ordinary PR checks and `npm run preflight:release` for focused release/package validation, with release automation docs describing when to use each command.
+- Why it matters: Maintainers and agents can catch recurring test, whitespace, release-versioning, and package dry-run issues before opening review.
+- Who is affected: Maintainers preparing ordinary PRs, release automation changes, package metadata changes, package contents changes, or publish workflow changes.
+- Action needed: Optional; run `npm run preflight` before ordinary review and `npm run preflight:release` before release/package review.
+- PR: #51
+
 ### 2026-06-21 — Maintainer Self-Profile Baseline
 
 - What changed: Added a repository self-profile for delivery-friction-analyzer so local self-analysis can classify normal development paths, functional surfaces, workflow context, and Conventional Commit-style PR classes.