@inetafrica/open-claudia 3.2.3 → 3.3.2

package/test-mandate-hygiene.js

@@ -63,13 +63,31 @@ assert.strictEqual(entities.readEntity("busy-contact").sections.Mandate, nearFul
 // ── no record: nothing to write to → refused with a reason ──
 const r4 = appendMandate({ entitySlug: "", personName: "" }, "anything");
 assert.strictEqual(r4.ok, false, "no contact record → refused");
-assert.ok(/no contact record/.test(r4.reason));
+assert.ok(/no linked contact record/.test(r4.reason));
 
-// ── legacy fallback: a record with only a personName still lands (by name) ──
+// ── name-only records are REFUSED, never name-keyed: a display name is
+// spoofable, and a name-keyed upsert could land security text on a same-named
+// OTHER person's note (v3.3.2 — this replaced the legacy fallback). ──
 const r5 = appendMandate({ entitySlug: "", personName: "Legacy Larry" }, "asking build status");
-assert.strictEqual(r5.ok, true, "name-only record still writes");
-assert.ok(/build status/.test((entities.readEntity("legacy-larry") || { sections: {} }).sections.Mandate || ""),
-  "fallback upserts the slugified-name entity");
+assert.strictEqual(r5.ok, false, "name-only record is refused");
+assert.ok(/no linked contact record/.test(r5.reason));
+assert.strictEqual(entities.readEntity("legacy-larry"), null,
+  "no entity is ever minted from a bare display name");
+
+// ── personId resolution: a record without an entitySlug resolves through the
+// person REGISTRY (id → entitySlug), never through the spoofable name ──
+const people = require("./core/people");
+const harry = people.add({ name: "Hash Harry" });
+people.setEntitySlug(harry.id, "hash-harry-9f9f9f");
+entities.upsertEntity({ slug: "hash-harry-9f9f9f", name: "Hash Harry", relationship: "external" });
+const r6 = appendMandate({ personId: harry.id, personName: "Spoofed Name" }, "asking build status");
+assert.strictEqual(r6.ok, true, "personId-only record resolves via the registry");
+assert.ok(/build status/.test(entities.readEntity("hash-harry-9f9f9f").sections.Mandate || ""),
+  "the grant lands on the person's registered slug");
+assert.strictEqual(entities.readEntity("spoofed-name"), null,
+  "the transport display name never picks the target");
+const r7 = appendMandate({ personId: "missing-person-id", personName: "Ghost" }, "anything");
+assert.strictEqual(r7.ok, false, "an unresolvable personId is refused, not name-keyed");
 
 // ── P3: capability-scoped grants — expiry, refresh, ids, revoke ──
 const mandates = require("./core/mandates");

package/test-provider-language.js

@@ -365,7 +365,31 @@ assert.match(pkg.description, /provider-agnostic coding-agent harness/i);
 // 2h); a lapsed deadline with a still-failing check fires the wake anyway as
 // a marked "Watch expired" prompt and removes the watch, so a watch whose
 // condition never comes true can no longer end silently.
-assert.strictEqual(pkg.version, "3.2.3", "release version must remain unchanged without explicit approval");
+// 3.3.0 cut 2026-08-14 (verify-contact batch: owner-only verify flow, HMAC
+// speaker attest on owner-gated loopback kinds, closed relay/transcript
+// egress) — but the release commit bumped package.json WITHOUT this pin, so
+// the tag's build job failed on this very assert: npm kept 3.2.3 and nothing
+// was published. Never retag a failed version — re-cut as +1.
+// 3.3.1 approved by Sumeet 2026-08-19 ("The tts timeout for long messages is
+// getting to be a problem Please fix it", with the sales-bot failure
+// screenshot): pocket TTS sentence-packs long text into ≤450-char chunks,
+// synthesizes each inside its own 120s window (one retry per chunk), and
+// ffmpeg-concats the wavs into ONE ogg — message length can no longer abort
+// the single gateway request and strand pods (no ElevenLabs key, no macOS
+// say) voiceless. Carries the unpublished 3.3.0 content plus the Kazee calls
+// batch (trickle ICE + streaming TTS playback, ringing-on-invite/deferred
+// publish, werift ICE rejection suppression). Plus this pin repair.
+// 3.3.2 approved by Sumeet 2026-08-20 ("Okay, I'll go with your
+// recommendations. Can you make sure you fix everything ... push everything
+// out once the new versions have landed for the dockers update the entire
+// fleet"): the identity/guardrail batch behind the Coders Africa incident —
+// transport-verified sender adoption (a known transport user id in an
+// adapter-attested DM is never interrogated; the router falls through and
+// handles the adopted turn), applyApproval mirrors person.isOwner instead of
+// demoting approved owners, and the mandate writer is strictly slug-keyed
+// (name-keyed fallback removed) with stranded dual-file grants surfaced on
+// the escalation card.
+assert.strictEqual(pkg.version, "3.3.2", "release version must remain unchanged without explicit approval");
 for (const keyword of ["claude", "codex", "coding-agent", "provider-agnostic"]) {
   assert.ok(pkg.keywords.includes(keyword), `package keyword missing: ${keyword}`);
 }