@vibe-monitor/setup 0.3.0-beta.21 → 0.3.0-beta.23
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 +5 -0
- package/dist/vibe-monitor.mjs +38 -38
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -131,6 +131,7 @@ node src/cli.js self-test
|
|
|
131
131
|
- `vibe_session_start`
|
|
132
132
|
- `vibe_checkpoint`
|
|
133
133
|
- `vibe_project_status`
|
|
134
|
+
- `vibe_version` (installed software version and update state)
|
|
134
135
|
- `vibe_findings`
|
|
135
136
|
- `vibe_explain_finding`
|
|
136
137
|
- `vibe_product_intent`
|
|
@@ -265,3 +266,7 @@ The first five new coverage families were also calibrated against Bloomroom and
|
|
|
265
266
|
9. Coding-agent neutral via MCP.
|
|
266
267
|
10. No coding session, no monitor process.
|
|
267
268
|
11. Monitoring has a budget: stay quiet when nothing meaningful changed and reuse unchanged work.
|
|
269
|
+
|
|
270
|
+
### Architecture Intelligence evidence (next release)
|
|
271
|
+
|
|
272
|
+
`vibe_explain_finding` now includes `explanation.signalDefinitions` (measurement meanings and limits), `explanation.sourceEvidence` (bounded file/line/source indicators), and `explanation.verificationContext` (including zero-test guidance). These indicators are evidence for review, not proof that a split is required. The `data-contract` monitor conservatively reports cross-file parsing of encoded identifiers with source lines; it does not automatically migrate IDs. `EVIDENCE_VERSION=5` invalidates old scan caches to recalculate findings. Concurrent identical cloud policy refreshes are coalesced while authorization remains fail-closed.
|