@compr/opscontext-mcp 2.0.1 → 2.0.2
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/CHANGELOG.md +30 -0
- package/dist/agents.js +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,36 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to OpsContext for AI Agents (previously ContextEngine — MCP server + CLI) are documented here.
|
|
4
4
|
|
|
5
|
+
## [2.0.2] — 2026-06-11 — HTML score report browser tab title → OpsContext
|
|
6
|
+
|
|
7
|
+
Tiny patch release. One change:
|
|
8
|
+
- `src/agents.ts` `generateScoreHTML()` — `<title>` tag changed from `ContextEngine Score Report` to `OpsContext Score Report`. Visible in the browser tab when a paying user (or the `score --html` CLI flag) generates the report. No functional change.
|
|
9
|
+
|
|
10
|
+
Why patch: cosmetic-only rename of a user-visible string. No new APIs, no contract changes, no behavior change for any caller.
|
|
11
|
+
|
|
12
|
+
Paired with the VS Code extension `0.8.1` release that adds the `OpsContext: Generate HTML Score Report (PRO)` command — together they close the visible-paid-feature gap from the 2.0.0 rebrand (advertised "HTML score reports — ✓" but no clickable path).
|
|
13
|
+
|
|
14
|
+
## [2.0.1] — 2026-06-11 — Flag day reached early + pricing href fix
|
|
15
|
+
|
|
16
|
+
### Changed
|
|
17
|
+
- **Legacy SHA-256 license signatures are now REJECTED** (the "flag day" originally scheduled for 2026-08-15). Brought forward to today because the production licence DB analysis showed the customer base is effectively empty — the only real active license belongs to the maintainer, who has already re-activated to Ed25519. Three other "active" rows in the DB are licenses that expired 2026-04-27 and are already failing the expiry check on every load. Bringing the flag day forward by ~10 weeks costs nothing real and removes the half-open security loophole sooner.
|
|
18
|
+
- `src/license-sig.ts` `verifyLicenseSignature()` — the 64-char hex branch now returns `{ ok: false, reason: "Legacy SHA-256 ... reactivate at ..." }` instead of `{ ok: true, mode: "legacy-grandfathered" }`.
|
|
19
|
+
- LOCK comment on the file updated: the flag-day-reached marker replaces the warning-about-grandfathering text.
|
|
20
|
+
- `src/activation.ts` `loadLicense()` — the `if (verify.mode === "legacy-grandfathered")` branch is now defensive dead code (kept since the union type still carries the variant for backward compat with audit-log records).
|
|
21
|
+
- `tests/license-sig.test.ts` — the test that previously asserted `mode: "legacy-grandfathered"` now asserts `ok: false` with a reactivation pointer in the reason. Test renamed `REJECTS legacy SHA-256 hex signature (flag day reached 2026-06-11)`.
|
|
22
|
+
- **Pricing URL href fix** in 5 source files. The user-facing strings referenced `https://compr.ch/contextengine/pricing` which returns 404; only `https://api.compr.ch/contextengine/pricing` resolves. Files: `src/activation.ts:145, 450`, `src/cli.ts:1882`, `src/index.ts:1132, 1170`.
|
|
23
|
+
- **`docs/deploy/ED25519_FLAG_DAY.md`** can now be archived — the action it scheduled was completed today. Leaving the file in place as a historical record.
|
|
24
|
+
- **`server/deploy.sh` hardened** (this was committed earlier as `bbeffe8`, but tying it to the release for context): pre-flight builds locally, smoke-tests `/health` after deploy and dies on broken state, uses the full PM2 path that actually works in non-interactive ssh shells. Supports `--dry-run`.
|
|
25
|
+
|
|
26
|
+
### Why this is patch-level, not minor
|
|
27
|
+
The behaviour change is a tightening of a check that was documented as temporary from day one. The semver contract said legacy signatures would be rejected after the flag day; the date moved up because the situation allowed it. No new features. No removed APIs.
|
|
28
|
+
|
|
29
|
+
### Notes
|
|
30
|
+
- 4 paying-customer rows in the activation DB; 1 is real and active (maintainer's enterprise license, already re-activated). The other 3 already expired April 27 and are non-active per the client's expiry check.
|
|
31
|
+
- Customer notification email (originally scheduled for 2026-08-08) skipped — would have been a no-op or a re-engagement note to the two `gmail.com` addresses whose licenses expired. Yannick can send re-engagement separately if he wants.
|
|
32
|
+
|
|
33
|
+
|
|
34
|
+
|
|
5
35
|
## [2.0.0] — 2026-06-10 — Strategic pivot + Claude Code native integration (A+B+C)
|
|
6
36
|
|
|
7
37
|
### Added (Claude Code integration — A + B + C from the rebrand backlog)
|
package/dist/agents.js
CHANGED
|
@@ -1546,7 +1546,7 @@ export function generateScoreHTML(scores) {
|
|
|
1546
1546
|
<head>
|
|
1547
1547
|
<meta charset="UTF-8">
|
|
1548
1548
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
|
1549
|
-
<title>
|
|
1549
|
+
<title>OpsContext Score Report</title>
|
|
1550
1550
|
<style>
|
|
1551
1551
|
:root {
|
|
1552
1552
|
--bg: #0f172a; --surface: #1e293b; --border: #334155;
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@compr/opscontext-mcp",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.2",
|
|
4
4
|
"description": "OpsContext for AI Agents — read-only fleet visibility (PM2/nginx/Docker/git/cron) + tamper-evident audit log + policy-as-code hooks. The ops + compliance layer Claude Code can't grow natively.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "dist/index.js",
|