delivery-friction-analyzer 0.14.0 → 0.14.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/package.json +1 -1
- package/release-log.md +8 -0
package/README.md
CHANGED
|
@@ -144,6 +144,8 @@ No separate model-ready context artifact is required for this workflow. Reconsid
|
|
|
144
144
|
|
|
145
145
|
## Development Notes
|
|
146
146
|
|
|
147
|
+
Repo-local maintainer and agent review expectations live in [AGENTS.md](AGENTS.md).
|
|
148
|
+
|
|
147
149
|
### Current Direction
|
|
148
150
|
|
|
149
151
|
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/package.json
CHANGED
package/release-log.md
CHANGED
|
@@ -2,6 +2,14 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
+
### 2026-06-21 — Repo-Specific Review Guidance
|
|
6
|
+
|
|
7
|
+
- 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.
|
|
8
|
+
- 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.
|
|
9
|
+
- Who is affected: Maintainers and agents preparing changes in this repository.
|
|
10
|
+
- Action needed: Optional; review `AGENTS.md` before broad, report/contract, profile, docs, or release/package changes.
|
|
11
|
+
- PR: #52
|
|
12
|
+
|
|
5
13
|
### 2026-06-21 — Local Preflight Commands
|
|
6
14
|
|
|
7
15
|
- 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.
|