@getmarrow/install 0.1.37 → 0.1.39
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 +27 -2
- package/package.json +1 -1
- package/src/installer.js +6 -3
package/README.md
CHANGED
|
@@ -70,6 +70,9 @@ Marrow's hosted API, website, and dashboard update automatically; local SDK depe
|
|
|
70
70
|
npx -y @getmarrow/install@latest activate
|
|
71
71
|
npx -y @getmarrow/install@latest doctor
|
|
72
72
|
|
|
73
|
+
# Measured API read health and local backlog
|
|
74
|
+
npx -y @getmarrow/mcp@latest ping
|
|
75
|
+
|
|
73
76
|
# Use only when doctor reports drift
|
|
74
77
|
npx -y @getmarrow/install@latest --repair
|
|
75
78
|
```
|
|
@@ -88,7 +91,29 @@ npx @getmarrow/install controller stop
|
|
|
88
91
|
|
|
89
92
|
Persistent controller lifecycle is currently Linux-only. On macOS or Windows, activation still installs and verifies the supported hooks without starting or signaling a background process; run `npx @getmarrow/install sidecar` under an owner-managed service and pass `--no-controller`. The controller does not silently upgrade packages, change governance policy, rotate credentials, or modify unrelated project configuration.
|
|
90
93
|
|
|
91
|
-
## What's New in v0.1.
|
|
94
|
+
## What's New in v0.1.39
|
|
95
|
+
|
|
96
|
+
v0.1.39 installs the bounded one-call passive read contract from day one:
|
|
97
|
+
|
|
98
|
+
- ordinary prompts receive one compact context read; risky or mutating prompts receive one fresh runtime gate instead;
|
|
99
|
+
- passive prompt telemetry is buffered locally rather than delaying the agent turn;
|
|
100
|
+
- transient read failures can use clearly labeled owner-only last-known guidance, while authentication failures never use cache;
|
|
101
|
+
- `doctor` prints the exact `npx -y @getmarrow/mcp@latest ping` command for measured current/p50/p99 latency, last success, and backlog health;
|
|
102
|
+
- certified hook commands pin MCP `3.9.55` and SDK `3.7.54` so advertised behavior matches the deployed server contract.
|
|
103
|
+
|
|
104
|
+
It preserves the intervention receipts introduced in v0.1.38.
|
|
105
|
+
|
|
106
|
+
## Previous: v0.1.38
|
|
107
|
+
|
|
108
|
+
v0.1.38 makes a meaningful Marrow intervention visible without adding manual work to routine agent sessions:
|
|
109
|
+
|
|
110
|
+
- generated instructions tell agents to retrieve and relay one factual intervention receipt after Marrow changes consequential work;
|
|
111
|
+
- Fleet Reports surface the same receipt for owners, including the required workflow, proof status, permit follow-through, and recorded outcome;
|
|
112
|
+
- agents remain quiet for routine low-risk work, and receipts exclude raw context, raw outcomes, proof values, credentials, and cross-tenant data.
|
|
113
|
+
|
|
114
|
+
It preserves the automatic local control lifecycle introduced in v0.1.37.
|
|
115
|
+
|
|
116
|
+
## Previous: v0.1.37
|
|
92
117
|
|
|
93
118
|
v0.1.37 adds the automatic local control lifecycle after explicit owner activation:
|
|
94
119
|
|
|
@@ -270,7 +295,7 @@ Supported integrations capture a compact lifecycle without storing raw prompts,
|
|
|
270
295
|
|
|
271
296
|
Meaningful work opens an outcome-closure item. A tool exit or workflow completion does not silently count as a successful business outcome; an explicit outcome receipt closes it. Transient delivery failures are held in an owner-only local spool and retried with the same event ID so retries do not create duplicate lifecycle records.
|
|
272
297
|
|
|
273
|
-
Owners can inspect pending outcomes in Fleet Operations. Agents can retrieve
|
|
298
|
+
Owners can inspect pending outcomes in Fleet Operations and recent intervention receipts in Reports. Agents can retrieve the same tenant-scoped receipt through the decision trace to explain what Marrow blocked, warned about, or held for review; the required workflow; proof status; permit follow-through; and the recorded outcome. The receipt excludes raw context, raw outcomes, proof values, credentials, and other tenants' data. Agents should relay one factual receipt summary after a meaningful intervention and stay quiet for routine low-risk work.
|
|
274
299
|
|
|
275
300
|
## Passive Token and Value Proof
|
|
276
301
|
|
package/package.json
CHANGED
package/src/installer.js
CHANGED
|
@@ -8,9 +8,9 @@ const { controllerStatus, controllerSupportedPlatform, ensureGovernanceControlle
|
|
|
8
8
|
const DEFAULT_BASE_URL = 'https://api.getmarrow.ai';
|
|
9
9
|
const MARROW_BLOCK_START = '<!-- marrow:passive-start -->';
|
|
10
10
|
const MARROW_BLOCK_END = '<!-- marrow:passive-end -->';
|
|
11
|
-
const MCP_ADAPTER_VERSION = '3.9.
|
|
12
|
-
const SDK_ADAPTER_VERSION = '3.7.
|
|
13
|
-
const SDK_ADAPTER_INTEGRITY = 'sha512-
|
|
11
|
+
const MCP_ADAPTER_VERSION = '3.9.55';
|
|
12
|
+
const SDK_ADAPTER_VERSION = '3.7.54';
|
|
13
|
+
const SDK_ADAPTER_INTEGRITY = 'sha512-KMgZEZpKo0AVKimXi4/SmtyPDV3mfx9hrj5drCdZxdNP8P/FL7ciyvyAEGiiXIMemh5Z3D/PUUvVO4jhr16ozQ==';
|
|
14
14
|
const SDK_ADAPTER_TARBALL = `https://registry.npmjs.org/@getmarrow/sdk/-/sdk-${SDK_ADAPTER_VERSION}.tgz`;
|
|
15
15
|
const MCP_PACKAGE_SPEC = `@getmarrow/mcp@${MCP_ADAPTER_VERSION}`;
|
|
16
16
|
const MCP_CONTEXT_HOOK_COMMAND = `npx -y ${MCP_PACKAGE_SPEC} context-hook`;
|
|
@@ -444,6 +444,7 @@ Marrow should run passively after install:
|
|
|
444
444
|
- Keep passive token/model usage proof enabled so Marrow can show token, cost, latency, and workflow savings after real work completes.
|
|
445
445
|
- Before risky work, use Marrow's decision brief or passive prompt hook.
|
|
446
446
|
- After meaningful work, record the outcome so future agents learn from it.
|
|
447
|
+
- After Marrow blocks, warns, or requires review, use the decision trace receipt to tell the operator what changed and which recorded workflow or proof is required. Stay quiet for routine low-risk work.
|
|
447
448
|
- Check health with \`marrow_agent_status\` or \`GET /v1/agent/status\`.
|
|
448
449
|
- When status/runtime returns a \`client_update\` notice, tell the operator and use its exact update and verification commands only when local change policy permits.
|
|
449
450
|
|
|
@@ -1530,6 +1531,7 @@ function printReport(report) {
|
|
|
1530
1531
|
if (report.doctor.envHints.length) process.stdout.write(`- possible env files: ${report.doctor.envHints.join(', ')}\n`);
|
|
1531
1532
|
process.stdout.write(`- missing hooks/config: ${report.doctor.missingHooks.length ? report.doctor.missingHooks.join('; ') : 'none'}\n`);
|
|
1532
1533
|
if (report.doctor.recommendedFix) process.stdout.write(`- recommended fix: ${report.doctor.recommendedFix}\n`);
|
|
1534
|
+
process.stdout.write(`- live health: ${report.doctor.healthCommand}\n`);
|
|
1533
1535
|
}
|
|
1534
1536
|
|
|
1535
1537
|
if (report.writeMode === 'dry-run') {
|
|
@@ -1684,6 +1686,7 @@ async function install(options) {
|
|
|
1684
1686
|
? `MARROW_API_KEY was found in a likely env file at ${envHints[0]}. Load that key from trusted secret storage, export only MARROW_API_KEY, then run npx @getmarrow/install --repair.`
|
|
1685
1687
|
: 'Set MARROW_API_KEY, then run npx @getmarrow/install --repair.'
|
|
1686
1688
|
: controller.exact_fix || selfTest.recommended_fix || null),
|
|
1689
|
+
healthCommand: 'npx -y @getmarrow/mcp@latest ping',
|
|
1687
1690
|
},
|
|
1688
1691
|
remediation,
|
|
1689
1692
|
configDiagnostics,
|