@dogpile/sdk 0.1.1 → 0.2.0

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.2.0
+
+- Prepared the Snow Leopard hardening release identity for `@dogpile/sdk@0.2.0` and `dogpile-sdk-0.2.0.tgz`.
+- Centralized release identity checks so manifest, README, changelog, package guard, package export tests, and pack metadata assertions drift together.
+- Normalized OpenAI-compatible fetch/network failures into stable `DogpileError` provider codes.
+- Tightened the publishable source allowlist so runtime test files stay out of the npm tarball.
+- Added a deterministic `pnpm run benchmark:baseline` timing harness for protocol-loop baseline comparisons without making a performance claim.
+- Corrected benchmark reproduction documentation paths and commands to point at the live `src/benchmark/config.test.ts` suite.
+
+## 0.1.2
+
+- Cleaned up the README release verification section so the npm package page has readable gate descriptions instead of a single dense paragraph.
+- Prepared the patch release identity for `@dogpile/sdk@0.1.2` and `dogpile-sdk-0.1.2.tgz`.
+
 ## 0.1.1
 
 - Updated npm package metadata after the GitHub repository transfer from `zakkeown/dogpile` to `bubstack/dogpile`.

package/README.md

@@ -102,22 +102,22 @@ pnpm run build
 pnpm pack --pack-destination ./packed
 ```
 
-The local tarball is named `dogpile-sdk-0.1.1.tgz` for the scoped package
-`@dogpile/sdk@0.1.1`. Install that tarball into a fresh consumer project:
+The local tarball is named `dogpile-sdk-0.2.0.tgz` for the scoped package
+`@dogpile/sdk@0.2.0`. Install that tarball into a fresh consumer project:
 
 ```sh
 mkdir ../dogpile-quickstart
 cd ../dogpile-quickstart
 pnpm init
-pnpm add ../dogpile/packed/dogpile-sdk-0.1.1.tgz
+pnpm add ../dogpile/packed/dogpile-sdk-0.2.0.tgz
 ```
 
 Equivalent install commands for other supported package managers are:
 
 ```sh
-npm install ../dogpile/packed/dogpile-sdk-0.1.1.tgz
-yarn add ../dogpile/packed/dogpile-sdk-0.1.1.tgz
-bun add ../dogpile/packed/dogpile-sdk-0.1.1.tgz
+npm install ../dogpile/packed/dogpile-sdk-0.2.0.tgz
+yarn add ../dogpile/packed/dogpile-sdk-0.2.0.tgz
+bun add ../dogpile/packed/dogpile-sdk-0.2.0.tgz
 ```
 
 ## Versioning and Stability
@@ -140,15 +140,27 @@ Before publishing, run the local package gates:
 pnpm run package:identity
 pnpm run package:artifacts
 pnpm run browser:smoke
+pnpm run benchmark:baseline
 pnpm run quickstart:smoke
 pnpm run verify
 pnpm run pack:check
 pnpm run publish:check
 ```
 
-`package:identity` asserts the scoped npm package name `@dogpile/sdk`, the current release identity, required package metadata (license, repository, keywords, publish access, and package manager), and scans release-facing source, docs, tests, and CI files for stale unscoped package install/import references. `package:artifacts` verifies that every runtime JavaScript file and TypeScript declaration file referenced by package metadata has been emitted by the build and is covered by `package.json` `files` before any pack or publish dry run. `browser:smoke` rebuilds the browser ESM bundle and runs the focused smoke test that imports `@dogpile/sdk` through the `browser` condition. `quickstart:smoke` builds the SDK, runs the package artifact guard, creates a real `pnpm pack` tarball, installs that tarball into a fresh temporary project without provider SDK peer fixtures, asserts the consumer dependency and lockfile resolve `@dogpile/sdk` from the `.tgz` instead of `workspace:` or `link:` metadata, verifies installed package entrypoints and `dist` imports do not resolve through local source imports, imports `@dogpile/sdk` from the consumer, imports every public package subpath from the installed tarball, extracts the marked quickstart from the installed package README, executes that documented provider-neutral `Dogpile.pile()` example end to end, writes a downstream TypeScript fixture that imports the package root and public subpaths, runs `tsc --noEmit` from the consumer project to prove declaration and export-map type resolution, verifies private helper files are absent from the installed tarball, and proves private helper subpaths remain blocked by package exports. `consumer:smoke` is kept as the same packed-tarball quickstart smoke command for compatibility. `verify` rebuilds `dist`, runs the package artifact guard, runs the packed-tarball quickstart smoke against that build, runs strict typecheck, then runs the test suite so declaration export checks, downstream type-resolution smoke tests, public API type-level assertions, the tarball install path, and package identity checks all fail the same local or CI gate. `pack:check` runs package identity, rebuilds `dist`, runs the package artifact guard before the packed-tarball quickstart smoke creates its `pnpm pack` tarball, then runs the packed JavaScript source-map and declaration-map guard and `npm pack --dry-run` so both the actual tarball install path and the npm package payload are checked. The source-map guard extracts the packed tarball, verifies every packaged `dist/**/*.js` and `dist/**/*.d.ts` file has its map, resolves packaged JavaScript and declaration `sourceMappingURL` references to map files present in the tarball, and confirms package-owned source references in those maps resolve to files present in the tarball. `publish:check` runs `verify`, reruns the package artifact guard, and then runs `npm publish --dry-run` so the package metadata, export map, and publishable files are checked without publishing.
+What each gate proves:
 
-The release identity is `@dogpile/sdk@0.1.1`. A real `pnpm pack` or `npm pack` for this scoped package produces the local tarball `dogpile-sdk-0.1.1.tgz`; the dry-run package gate must report that tarball filename and the scoped npm package name before publish. See `CHANGELOG.md` for release notes and breaking-change documentation.
+- `package:identity` asserts the scoped npm package name `@dogpile/sdk`, the current release identity, required package metadata, and release-facing references in source, docs, tests, and CI.
+- `package:artifacts` verifies that package metadata references only emitted runtime JavaScript and TypeScript declaration files covered by `package.json` `files`.
+- `browser:smoke` rebuilds the browser ESM bundle and imports `@dogpile/sdk` through the package root `browser` condition.
+- `benchmark:baseline` rebuilds `dist`, runs the deterministic protocol-loop timing harness, and prints repeatable JSON for local before/after comparisons.
+- `quickstart:smoke` creates a real `pnpm pack` tarball, installs it into a fresh consumer project, and asserts the dependency and lockfile resolve `@dogpile/sdk` from the `.tgz` instead of `workspace:` or `link:` metadata.
+- `quickstart:smoke` also verifies installed entrypoints and `dist` imports do not resolve through local source imports, imports every public package subpath from the installed tarball, runs the marked README quickstart, runs `tsc --noEmit` from the consumer project, verifies private helper files are absent from the installed tarball, and proves private helper subpaths remain blocked by package exports.
+- `consumer:smoke` is kept as the same packed-tarball quickstart smoke command for compatibility.
+- `verify` rebuilds `dist`, runs the package artifact guard, runs the packed-tarball quickstart smoke, runs strict typecheck, and then runs the test suite.
+- `pack:check` runs package identity, rebuilds `dist`, verifies package artifacts, runs the packed-tarball quickstart smoke, checks packed JavaScript source maps and declaration maps, and finishes with `npm pack --dry-run`.
+- `publish:check` runs `verify`, reruns the package artifact guard, and then runs `npm publish --dry-run` so the package metadata, export map, and publishable files are checked without publishing.
+
+The release identity is `@dogpile/sdk@0.2.0`. A real `pnpm pack` or `npm pack` for this scoped package produces the local tarball `dogpile-sdk-0.2.0.tgz`; the dry-run package gate must report that tarball filename and the scoped npm package name before publish. See `CHANGELOG.md` for release notes and breaking-change documentation.
 
 The browser ESM target is emitted at `dist/browser/index.js` with `dist/browser/index.js.map`; both the package root `browser` condition and the explicit `@dogpile/sdk/browser` subpath resolve to that bundled artifact.