@estiva-app/protocol 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -4,6 +4,37 @@ Every entry answers the wire question explicitly, including when the answer is
 nothing (ADR 0002 §4b). A change to the bytes an app publishes is a MAJOR — in
 `0.x`, a MINOR — even when no TypeScript signature moved.
 
+## 0.1.1 — 2026-08-27
+
+**Wire behaviour: unchanged.** Nothing in `src/` changed except the version
+constant. The `dist/` a consumer receives is byte-identical to 0.1.0's apart from
+that string, and no builder, tag layout, id computation or signature input moved.
+
+**This release exists to exercise the release path, and that is the honest
+description of it.** ADR 0002 §4c decided that releases publish through trusted
+publishing (OIDC) with no npm credential in GitHub. 0.1.0 could not test that: a
+package's first publish is necessarily manual, because a trusted publisher is
+configured on a package that already exists. So until this tag, §4c was a
+decision nobody had executed, and the trusted publisher was configured and
+unexercised — the state in which a misconfiguration is cheapest to find and most
+likely to be discovered at the worst moment instead.
+
+What it carries, for completeness rather than as a reason to upgrade:
+
+- **`npm run typecheck` worked in CI and failed on a fresh clone.** It was
+  `tsc -p tsconfig.json --noEmit && tsc -p tsconfig.test.json`; the second pass
+  typechecks `test/**/*.ts`, which import `../dist/index.js` on purpose because
+  dist is what ships, so TypeScript resolves them to `dist/index.d.ts` — which
+  does not exist until something builds. CI runs `build` first, so it was green.
+  A fresh clone got eleven `TS2307`s that read as a broken package. Now
+  `npm run build && tsc -p tsconfig.test.json`, which is one `tsc` invocation
+  fewer, since the build already typechecks `src`.
+
+**A consumer on `^0.1.0` needs to do nothing.** The range already admits this
+version, neither changed file ships in the tarball's functional surface
+(`tsconfig.test.json` is not in `files`, and `scripts` do not run for a
+consumer), and the only observable difference is `PROTOCOL_VERSION`.
+
 ## 0.1.0 — 2026-08-27
 
 First release. SHA-3.

package/dist/index.d.ts

@@ -46,7 +46,7 @@
 /** Bumped by hand with the version in package.json — `test/version.test.ts`
  * pins the two together. It exists so "the upgrade reached the app" can be
  * checked by grepping a built bundle rather than by trusting a lockfile. */
-export declare const PROTOCOL_VERSION = "0.1.0";
+export declare const PROTOCOL_VERSION = "0.1.1";
 export { type NostrTag, type UnsignedEvent, type SignedEvent, type Profile, type ThreadRef, type ChannelVisibility, type ChannelKind, type MemberRole, type Label, type ResolutionAction, KIND, MAX_EMOJI_CHARS, MAX_MESSAGE_BYTES, MAX_MENTIONS, MAX_RATIONALE_BYTES, RELAY_AUTH_TOLERANCE_SECS, ASSERTION_SUBTYPE, computeEventId, toNostrSeconds, canonicalChannelName, threadTags, addr, relayAuthUrl, buildProfile, parseProfile, buildCreateChannel, buildDeleteChannel, buildEditChannelMetadata, buildAddMember, buildReaction, buildDeletion, buildMessage, buildResolution, buildFile, buildComponent, buildHighlight, buildUnsignedRelayAuthEvent, } from './events.js';
 export { type AddressPointer, convertBits, bech32Encode, bech32Decode, encodeNaddr, decodeNaddr, pointerToAddress, addressToPointer, addrToNaddr, naddrToAddr, referenceToPointer, NADDR_RE, findNaddrs, stripNaddrs, } from './nip19.js';
 export { type AuthEventArgs, TIMESTAMP_TOLERANCE_SECS, normalizeUrl, buildUnsignedAuthEvent, base64, authorizationHeaderFor, authorizationHeader, } from './nip98.js';

package/dist/index.js

@@ -46,7 +46,7 @@
 /** Bumped by hand with the version in package.json — `test/version.test.ts`
  * pins the two together. It exists so "the upgrade reached the app" can be
  * checked by grepping a built bundle rather than by trusting a lockfile. */
-export const PROTOCOL_VERSION = '0.1.0';
+export const PROTOCOL_VERSION = '0.1.1';
 export { 
 // constants
 KIND, MAX_EMOJI_CHARS, MAX_MESSAGE_BYTES, MAX_MENTIONS, MAX_RATIONALE_BYTES, RELAY_AUTH_TOLERANCE_SECS, ASSERTION_SUBTYPE, 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@estiva-app/protocol",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "The Estiva wire format: Buzz-shaped Nostr event builders, NIP-01 ids, NIP-19 naddr, NIP-98 HTTP auth, and the relay clients. Speaks the protocol; interprets nothing.",
   "license": "MIT",
   "type": "module",
@@ -43,7 +43,7 @@
   "scripts": {
     "build": "tsc -p tsconfig.json",
     "test": "npm run build && node --test test/*.test.mjs test/*.test.ts",
-    "typecheck": "tsc -p tsconfig.json --noEmit && tsc -p tsconfig.test.json",
+    "typecheck": "npm run build && tsc -p tsconfig.test.json",
     "prepublishOnly": "npm run build",
     "verify:live": "node scripts/verify-live.mjs"
   },

package/src/index.ts

@@ -47,7 +47,7 @@
 /** Bumped by hand with the version in package.json — `test/version.test.ts`
  * pins the two together. It exists so "the upgrade reached the app" can be
  * checked by grepping a built bundle rather than by trusting a lockfile. */
-export const PROTOCOL_VERSION = '0.1.0'
+export const PROTOCOL_VERSION = '0.1.1'
 
 export {
   // types