@wenathlan/saddle 1.8.11 → 1.8.13

package/docs/actionrecorder.md

@@ -0,0 +1,12 @@
+# Action recorder
+
+The browser `actionrecorder` links actions to the snapshot, tab, frame and window context that preceded them. The optional `maxevents` limit keeps long sessions bounded by dropping the oldest events and reporting the number dropped in the manifest.
+
+```ts
+const recorder = actionrecorder({ maxevents: 2000 });
+recorder.snapshot(snapshot);
+recorder.action({ action: "click", payload: { ref: "e1" } });
+const archive = recorder.exportjson();
+```
+
+`manifest()` and `exportjson()` return copies of the recorded payloads. `clear()` resets the event stream and correlation boundary. The recorder remains an in-memory, caller-owned component; it does not select a browser, persistence backend or credential.

package/docs/artifactavailability.md

@@ -62,4 +62,55 @@ Version 1.8.11 keeps the Tauri browser build flat at `desktop/`, with `Cargo.tom
 
 The Android project maps Saddle-owned `AndroidManifest.xml`, `main/`, `res/`, `test/` and `androidtest/` directly from the `android/` root through Gradle `sourceSets`. Capacitor staging under `android/app`, `android/assets` and plugin internals is generated during synchronization, removed or ignored before build, and is not project-owned source. The iOS surface keeps its generated Xcode and Swift Package internals because Capacitor owns those paths; Saddle-owned configuration remains at the `ios/` root and no project-owned `ios/src` directory is added.
 
-The v1.8.11 workflows derive the version from the release tag, run flat-surface validation, reject helper binaries and attach only outputs matching the dotted lowercase contract. The live release asset list must be verified before this section is changed from a source contract to a generated asset inventory.
+The v1.8.11 workflows derive the version from the release tag, run flat-surface validation, reject helper binaries and attach only outputs matching the dotted lowercase contract. The live release asset list below was verified against the published GitHub release.
+
+## Verified 1.8.11 primary assets
+
+Sizes are bytes and exclude the separate manifest and checksum files.
+
+| Surface         | Asset                                                                                                       |       Size |
+| --------------- | ----------------------------------------------------------------------------------------------------------- | ---------: |
+| Desktop browser | [AppImage](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.browser.1.8.11.appimage)    | 79,870,456 |
+| Desktop browser | [Debian](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.browser.1.8.11.deb)           |  5,294,158 |
+| Desktop browser | [RPM](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.browser.1.8.11.rpm)              |  5,297,619 |
+| Desktop browser | [Windows EXE](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.browser.1.8.11.exe)      |  4,343,237 |
+| Desktop browser | [Windows MSI](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.browser.1.8.11.msi)      |  5,246,976 |
+| Desktop browser | [macOS DMG](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.browser.1.8.11.dmg)        |  5,216,935 |
+| Android         | [APK](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.apk.1.8.11.apk)                  |  3,498,594 |
+| Android         | [AAB](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.aab.1.8.11.aab)                  |  3,893,324 |
+| Container       | [OCI tarball](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.container.1.8.11.tar.gz) | 81,722,975 |
+| Extension       | [ZIP](https://github.com/wenathlan/saddle/releases/download/v1.8.11/saddle.extension.1.8.11.zip)            |     10,760 |
+
+The release also contains `manifest.*.1.8.11.json` and `sha256.*.1.8.11` files for Android, container, and each desktop runner. No IPA was attached because caller-owned Apple signing and provisioning were not enabled for this release.
+
+## 1.8.12 release matrix
+
+Version 1.8.12 is prepared to publish the expanded matrix below. The release workflows derive the version from the `v1.8.12` tag and generate the checksum and manifest files beside each surface artifact. Sizes and final signing states remain pending until the release workflows complete; this section does not claim that an artifact exists before CI attaches it.
+
+| Surface | Architectures | Artifact naming contract |
+| --- | --- | --- |
+| Linux desktop browser | x64, arm64 | `saddle.browser.1.8.12.<architecture>.deb`, `.rpm`, `.appimage` |
+| Windows desktop browser | x86, x64, arm64 | `saddle.browser.1.8.12.<architecture>.exe`, `.msi` |
+| macOS desktop browser | x64, arm64 | `saddle.browser.1.8.12.<architecture>.dmg`, `.app.zip` |
+| Android | caller-configured signing | `saddle.apk.1.8.12.apk`, `saddle.aab.1.8.12.aab` |
+| iOS | caller-configured signing and provisioning | `saddle.ipa.1.8.12.ipa`, `saddle.app.1.8.12.app.zip` |
+| Container | OCI | `saddle.container.1.8.12.tar.gz` |
+| Browser extension | Manifest V3 | `saddle.extension.1.8.12.zip` |
+
+Each surface also emits `sha256.*.1.8.12`, `manifest.*.1.8.12.json` and, where enabled by the release path, SBOM and provenance metadata. The manifest must state `unsigned`, `ci-test-key`, `caller-owned`, `notarized` or the verified provider status actually produced by CI.
+
+## 1.8.13 release matrix
+
+Version 1.8.13 keeps the release-tag-derived matrix and adds deterministic retention metadata to generated artifact manifests. The implementation records retention policy and keep/prune decisions but never removes caller-owned files. Final URLs, checksums, sizes and signing states remain pending until the corresponding release workflow completes.
+
+| Surface | Architectures | Artifact naming contract |
+| --- | --- | --- |
+| Linux desktop browser | x64, arm64 | `saddle.browser.1.8.13.<architecture>.deb`, `.rpm`, `.appimage` |
+| Windows desktop browser | x86, x64, arm64 | `saddle.browser.1.8.13.<architecture>.exe`, `.msi` |
+| macOS desktop browser | x64, arm64 | `saddle.browser.1.8.13.<architecture>.dmg`, `.app.zip` |
+| Android | caller-configured signing | `saddle.apk.1.8.13.apk`, `saddle.aab.1.8.13.aab` |
+| iOS | caller-configured signing and provisioning | `saddle.ipa.1.8.13.ipa`, `saddle.app.1.8.13.app.zip` |
+| Container | OCI | `saddle.container.1.8.13.tar.gz` |
+| Browser extension | Manifest V3 | `saddle.extension.1.8.13.zip` |
+
+Each surface also emits `sha256.*.1.8.13`, `manifest.*.1.8.13.json` and, where enabled by the release path, SBOM and provenance metadata. The manifest may additionally carry `retention`, `retentionplan` and `retentionevaluatedat`; these fields are advisory execution decisions and do not imply deletion or publication.

package/docs/batches-1816-1820.md

@@ -0,0 +1,13 @@
+# Objective driven batches 1.8.16 to 1.8.20
+
+The uploaded scope README remains an objective reference. It describes the intended package behavior, runtime independence, storage-to-compute bridge and public target surfaces; it does not prescribe a deterministic file sequence or implementation recipe.
+
+| Batch | Selected objective | Acceptance evidence |
+|---|---|---|
+| 1.8.16 | Complete the generic S3-compatible storage surface with caller-signed paginated listing. | XML listing fixtures, prefix and continuation handling, malformed-response errors and adapter contract tests. |
+| 1.8.17 | Make sitemap index traversal bounded, recursive, deduplicated and cycle-safe. | Nested index fixtures, duplicate URLs, cycles, `maxUrls` and network-error tests. |
+| 1.8.18 | Make browser action recording bounded and exportable without losing snapshot correlation. | Event limit, clear/export behavior, immutable manifest copies and correlation tests. |
+| 1.8.19 | Add explicit workflow input validation and deterministic trigger matching for caller-owned CI dispatch. | Strict input fixtures, unknown input rejection, event filtering and registry tests. |
+| 1.8.20 | Add a cross-runtime capability report for library, browser, desktop, mobile, CLI and binary modes. | Stable capability matrix, caller overrides and no host, port or credential ownership. |
+
+The batches are deliberately grouped by objective rather than by a fixed folder plan. Each batch must pass focused tests before the next batch is selected. Version bumps, commits, tags and releases remain separate delivery actions and wait for the user's explicit authorization.

package/docs/capabilityreport.md

@@ -0,0 +1,13 @@
+# Capability report
+
+The `capabilityreport` contract produces a stable, serializable view of the execution, runtime, memory, file, dependency, visibility and pairing axes. It resolves every execution mode with caller-selected overrides and exposes the effective boolean capabilities for diagnostics, documentation and adapters.
+
+```ts
+const report = capabilityreport({
+  runtime: "unknown",
+  memory: "external",
+  pair: "with",
+});
+```
+
+The report explicitly labels host, port, credentials and provider as caller-owned. It does not start a process, open a socket, select a cloud service or promise that every target has an installed toolchain. It describes the library contract and preserves user choice across browser, desktop, mobile, CLI, binary and application modes.

package/docs/documentmap-1.8.12.md

@@ -0,0 +1,17 @@
+# Document map for 1.8.12
+
+## Canonical root documents
+
+Project policies, notices and contribution guidance remain at the repository root so package consumers and forge interfaces can discover them without entering `docs`. The canonical license is the extensionless `LICENSE` file containing the official unmodified GNU GPL v3.0 text. Human-readable project policies use one Markdown file per context: `acceptable-use-policy.md`, `authors.md`, `bug-report.md`, `cla.md`, `code-of-conduct.md`, `contributing.md`, `copyright.md`, `disclaimer.md`, `eula.md`, `export-control.md`, `governance.md`, `notice.md`, `privacy-policy.md`, `pull-request-template.md`, `security.md`, `support.md`, `terms-and-conditions.md`, `terms-of-use.md`, `third-party-notices.md` and `trademark-policy.md`.
+
+The public scope README remains `/home/ubuntu/upload/README.md` and was not modified. The repository's own `README.md` remains a public project document and can receive release or signing-policy updates separately from the immutable scope reference.
+
+## Removed exact duplicates
+
+The following root `.txt` files were byte-identical copies of their Markdown counterparts and were removed: `authors.txt`, `code-of-conduct.txt`, `contributing.txt`, `copyright.txt`, `disclaimer.txt`, `notice.txt`, `privacy-policy.txt`, `security.txt`, `terms-and-conditions.txt`, `terms-of-use.txt` and `trademark-policy.txt`. The old `license.md` and `license.txt` were also removed because they duplicated a now-canonical root license context while carrying the obsolete proprietary view-only text.
+
+The README files under `docs/plans` and `docs/talks9` were not treated as root policy duplicates. They preserve plan or conversation context and are intentionally outside the root legal-document set.
+
+## Policy rule
+
+A policy document may describe repository operations, hosted-service behavior, privacy, security, trademarks or community conduct, but it must not revoke rights granted by GPL-3.0-only. Third-party component licenses remain separate and are recorded through package manifests, lockfiles and release inventories.

package/docs/licenseaudit-1.8.12.md

@@ -0,0 +1,21 @@
+# License audit for 1.8.12
+
+## Current repository state
+
+The repository contains three project license copies: `LICENSE`, `license.md` and `license.txt`. All three describe a custom Proprietary Source-Available License, View Only. They explicitly state that the software is not open source and prohibit copying, execution, modification, distribution and internal business use without written permission. `license.md` and `license.txt` contain minor author and link differences from `LICENSE`.
+
+The package manifests do not match those documents. `package.json` declares `GPL-3.0-only`, `pom.xml` declares GNU GPL v3.0, `saddle.csproj` declares `GPL-3.0-only`, and `saddle.gemspec` declares `GPL-3.0`. This is a material licensing contradiction that must be resolved before a new release is tagged.
+
+## Verified policy distinction
+
+The Open Source Initiative requires an open source license to allow free redistribution, source distribution, derived works, and use in any field of endeavor, including business use [1]. The GNU GPL v3 grants permission to run and modify covered works and allows private works that are not conveyed without additional conditions; distribution activates the license obligations [2].
+
+Therefore, “open source but only for our private use” is not one coherent license policy. A private or internal deployment is compatible with GPL use, but a license that prohibits other people from using, copying, modifying or distributing the software is source-available/proprietary, not OSI open source. The repository must choose one policy and express it consistently across the three license files, manifests, package metadata, README references and provider applications.
+
+SignPath Foundation requires an OSI-approved open source license without commercial dual licensing for all components. It also requires active maintenance, an existing release, documented functionality, a public code-signing policy, verifiable builds and manual approval for every signed release [3]. The current view-only license would therefore be incompatible with the free SignPath Foundation route until the repository adopts and consistently declares an OSI-approved license.
+
+## References
+
+[1]: https://opensource.org/osd "Open Source Initiative: The Open Source Definition"
+[2]: https://www.gnu.org/licenses/gpl-3.0.html "Free Software Foundation: GNU General Public License version 3"
+[3]: https://signpath.org/terms.html "SignPath Foundation: Conditions for Open Source projects"

package/docs/memoryengine.md

@@ -0,0 +1,21 @@
+# Memory engine
+
+The `memoryengine` contract keeps a hot working set in process memory while using caller-owned storage backends as the durable side of the bridge. With no limits, the engine preserves its historical behavior. With `maxentries` or `maxbytes`, it evicts the least recently used object after a load or persist operation exceeds the selected bound.
+
+```ts
+import { memoryengine } from "@wenathlan/saddle";
+
+const memory = memoryengine({
+  backends: [storage],
+  maxentries: 128,
+  maxbytes: 64 * 1024 * 1024,
+});
+
+await memory.persist("job-output", payload, { mimetype: "application/json" });
+const object = await memory.load("job-output");
+console.log(memory.stats());
+```
+
+Eviction affects only the hot in-process cache. The engine persists data to every configured backend before updating the cache, and a later load can rehydrate an evicted object from the first backend that returns it. `stats()` reports entries, bytes, cache hits, cache misses, evictions and configured limits so a caller can tune the working set without treating storage as physical RAM.
+
+The limits are optional non-negative integers. A payload larger than `maxbytes` remains persisted but is not retained in the hot cache. The engine does not create a host, port, credential, storage account or provider binding on behalf of the caller.

package/docs/nativeidentityresearch-1.8.11.md

@@ -0,0 +1,69 @@
+# Saddle native identity research
+
+## OpenCode comparison
+
+The public OpenCode repository documents a desktop distribution alongside its CLI and package-manager routes. Its documented desktop matrix includes macOS Apple Silicon and Intel DMG installers, a Windows x64 executable, and Linux DEB, RPM and AppImage outputs. The comparison supports explicit platform and architecture naming in Saddle release assets, but it does not justify copying OpenCode branding, icons or implementation.
+
+Source: [OpenCode repository and README](https://github.com/anomalyco/opencode)
+
+## ZCode comparison
+
+The public ZCode installation guide presents separate downloads for macOS Apple Silicon, macOS Intel, Windows x64, Windows ARM64 and Linux x64. Its Linux guidance uses an AppImage, while macOS uses a DMG to install an `.app` bundle and Windows uses an installer. This supports adding architecture-aware artifact labels and an explicit `.app` packaging path where the Apple runner supports it.
+
+Source: [ZCode official installation guide](https://zcode.z.ai/en/docs/install)
+
+## Saddle decisions
+
+Saddle keeps one shared TypeScript library-first engine and uses flat, surface-owned build roots. The release matrix should distinguish architecture from package format, for example `saddle.browser.1.8.11.windows.x64.exe` and `saddle.browser.1.8.11.windows.arm64.exe`, instead of hiding architecture in a generic filename. The workflow must publish only artifacts actually built by the runner and must not claim a valid signature when signing credentials are absent.
+
+Windows Authenticode, macOS Developer ID signing and notarization, Android release signing, and Apple provisioning remain caller-owned secret contracts. Public workflows can validate certificate presence, signer identity, timestamping and notarization status without embedding keys or manufacturing trust signals.
+
+## Official signing constraints
+
+Microsoft documents that Smart App Control accepts RSA-based code-signing certificates and does not currently support ECC signatures for this check. Trusted Signing is the preferred Microsoft route, while `signtool.exe` remains the command-line path for certificate-backed signing. An unsigned or locally signed binary cannot honestly be presented as trusted by the Saddle workflow.
+
+Apple documents that macOS software distributed with Developer ID must be notarized, and that notarization scans for malicious components and code-signing issues. A production workflow therefore needs Developer ID signing, hardened runtime, a secure timestamp, notarization through `notarytool` or an equivalent service, and ticket stapling before the artifact is labeled notarized.
+
+Sources: [Microsoft Smart App Control code signing](https://learn.microsoft.com/en-us/windows/apps/develop/smart-app-control/code-signing-for-smart-app-control) and [Apple notarizing macOS software](https://developer.apple.com/documentation/security/notarizing-macos-software-before-distribution).
+
+## Windows without a private certificate
+
+Microsoft's current comparison states that an MSIX package submitted through the Microsoft Store is re-signed by Microsoft at no certificate cost to the publisher. The same free treatment does not apply to an MSI or EXE submitted through the Store: those installers must already chain to a certificate trusted by Microsoft's root program. For direct distribution, Microsoft lists Azure Artifact Signing, traditional OV certificates, self-signed certificates and unsigned binaries as different trust levels; self-signed and unsigned outputs are for development or testing, not public trust. The page also identifies the SignPath Foundation as an open-source route worth evaluating rather than pretending that a generated self-signed key removes SmartScreen warnings.
+
+Source: [Microsoft code signing options for Windows app developers](https://learn.microsoft.com/en-us/windows/apps/package-and-deploy/code-signing-options).
+
+## Apple distribution without an owned certificate
+
+Apple's Developer ID guidance states that Gatekeeper checks for a Developer ID certificate when software is distributed outside the Mac App Store. The Developer ID certificate is generated from an Apple Developer account by the Account Holder, and notarization scans Developer ID-signed software before Apple issues the ticket used by Gatekeeper. There is no public framework that manufactures an Apple-trusted Developer ID certificate for an unrelated project. An open-source project must either distribute through the Mac App Store, use an authorized organization account, or publish an unsigned/test artifact with an explicit warning.
+
+Source: [Apple Developer ID signing and notarization](https://developer.apple.com/developer-id/).
+
+## Android distribution without owning the Play signing key
+
+Android still requires every installable APK to be digitally signed. Google Play App Signing changes who protects the production app-signing key: the publisher keeps an upload key, while Google signs the distributed APKs. This helps an open-source project avoid operating the final Play signing key, but it does not remove the need for a Play Console account, an upload key and a release identity. Direct APK distribution outside Google Play still requires Saddle to sign the APK itself.
+
+Source: [Android app signing and Play App Signing](https://developer.android.com/studio/publish/app-signing).
+
+## Open-source Windows certificate route
+
+The SignPath Foundation states that it can provide code-signing certificates for eligible open-source projects, keeps the private key in its hardware security module and verifies that the binary came from the project's public repository. This is a real external approval program, not a library that generates a universally trusted certificate locally. Saddle can apply to the program, but the workflow must remain disabled or unsigned until the project is accepted and the provider-specific integration is configured.
+
+Source: [SignPath Foundation](https://signpath.org/).
+
+## What the OpenCode workflow actually does
+
+The public OpenCode publish workflow invokes `azure/artifact-signing-action` with an Azure Trusted Signing endpoint, account name and certificate profile. This explains how a visible open-source project can distribute signed Windows binaries: the project has access to an external signing service and repository or organization secrets. It is not evidence that OpenCode generates a universally trusted certificate from source code. Saddle can follow the same pattern after an Azure Artifact Signing or SignPath application is approved, but must keep its unsigned mode until then.
+
+Source: [OpenCode publish workflow](https://raw.githubusercontent.com/anomalyco/opencode/dev/.github/workflows/publish.yml).
+
+## What the Zed workflow demonstrates
+
+The public Zed post-release workflow focuses on refreshing release pages, publishing a WinGet manifest and deploying documentation. It references organization secrets for those integrations and does not expose a locally generated signing certificate. This is consistent with the broader pattern: open-source projects can publish broadly, but platform trust comes from a store, a managed signing provider or a certificate held by the project organization.
+
+Source: [Zed post-release workflow](https://raw.githubusercontent.com/zed-industries/zed/main/.github/workflows/after_release.yml).
+
+## Safe GitHub Actions secret handling
+
+GitHub's documentation says repository or environment secrets are created from the repository Settings page and injected through the `secrets` context. Secrets are not passed to fork-triggered workflows or Dependabot events, and GitHub recommends OIDC for cloud providers that support it so long-lived credentials can be avoided. Saddle must therefore configure signing only on trusted release events, never expose values in command arguments or logs, and keep manual test keys separate from production signing credentials.
+
+Source: [Using secrets in GitHub Actions](https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets).

package/docs/releaseassets.md

@@ -1,10 +1,10 @@
 # Release assets
 
-The Node-only release adapter creates deterministic metadata for caller-selected artifacts. For version `1.8.11`, it writes dotted surface-specific names such as `sha256.desktop.1.8.11`, `manifest.desktop.1.8.11.json`, `sbom.desktop.1.8.11.cdx.json` and `provenance.desktop.1.8.11.intoto.jsonl`. The adapter rejects underscore-based public names and Rust build-helper executables. It never publishes, authenticates or selects a registry.
+The Node-only release adapter creates deterministic metadata for caller-selected artifacts. For version `1.8.12`, it writes dotted surface-specific names such as `sha256.desktop.1.8.12`, `manifest.desktop.1.8.12.json`, `sbom.desktop.1.8.12.cdx.json` and `provenance.desktop.1.8.12.intoto.jsonl`. The adapter rejects underscore-based public names and Rust build-helper executables. It never publishes, authenticates or selects a registry.
 
 ```bash
 npm run release:assets -- \
-  --version 1.8.11 \
+  --version 1.8.12 \
   --surface desktop \
   --output build/release \
   --artifact build/saddle.tgz \
@@ -15,3 +15,7 @@ npm run release:assets -- \
 The artifact paths are supplied by the caller and are sorted before the checksum, manifest, SBOM and provenance files are written. Package dependencies are read from the root lockfile to build a compact component list. The output can be attached to a release or checked by a registry-specific workflow without adding credentials to the library.
 
 The package also exports the adapter as `@wenathlan/saddle/release-assets`. It is intentionally Node-only because release metadata reads files and uses the Node crypto implementation; the transport-neutral root remains free of Node imports.
+
+## Release matrix
+
+The `releaseartifactmatrix(version, options)` contract in `packager/manifest.ts` describes the supported desktop, Android, iOS, container and browser-extension outputs in one deterministic structure. Each entry includes platform, architecture, dotted artifact names, checksum name, manifest name and the actual signing label supplied by the caller. It is descriptive only: it does not invoke a vendor toolchain, select a registry or imply that a platform trusts an unsigned artifact.

package/docs/releasenotes-1.8.12.md

@@ -0,0 +1,46 @@
+# Saddle 1.8.12
+
+Saddle 1.8.12 consolidates the root-first native surfaces, the GPL-3.0-only project policy, release provenance and the cross-platform artifact contract. The package manifest and active native manifests remain at `1.8.12`. The uploaded scope README is not an execution script and was not rewritten.
+
+## Highlights
+
+| Area | Change |
+|---|---|
+| Licensing | Canonical GPL-3.0-only license, aligned package metadata and consolidated root legal documents. |
+| Release verification | Independent checksum, manifest and explicit signing-state verification. |
+| Storage | Paginated S3-compatible listing with prefix, continuation token, XML entity decoding and caller-owned limits. |
+| Scraping | Bounded recursive sitemap traversal with deduplication, cycle protection and injected fetcher. |
+| Browser | Bounded action recorder with immutable manifests, JSON export and explicit clearing. |
+| Workflows | Strict typed inputs, defaults, choices and deterministic trigger identities. |
+| Modes | Cross-runtime capability report with caller-owned host, port, credentials and provider boundaries. |
+| Security | Existing CodeQL, OSV, npm audit, cargo audit, Trivy, SBOM and provenance gates remain active. |
+
+## Artifact matrix
+
+The release workflows derive the version from the release tag and use these lowercase dotted names. This table is the contract expected from CI; it does not claim that an asset exists until the corresponding workflow attaches it.
+
+| Surface | Architectures or mode | Expected artifact |
+|---|---|---|
+| Linux desktop browser | x64, arm64 | `saddle.browser.1.8.12.<architecture>.deb`, `.rpm`, `.appimage` |
+| Windows desktop browser | x86, x64, arm64 | `saddle.browser.1.8.12.<architecture>.exe`, `.msi` |
+| macOS desktop browser | x64, arm64 | `saddle.browser.1.8.12.<architecture>.dmg`, `.app.zip` |
+| Android | caller-configured signing | `saddle.apk.1.8.12.apk`, `saddle.aab.1.8.12.aab` |
+| iOS | caller-configured signing and provisioning | `saddle.ipa.1.8.12.ipa`, `saddle.app.1.8.12.app.zip` |
+| Container | OCI | `saddle.container.1.8.12.tar.gz` |
+| Browser extension | Manifest V3 | `saddle.extension.1.8.12.zip` |
+
+Each generated surface must carry its checksum and manifest companion. Where enabled, CI also emits SBOM and provenance metadata. The signing state must be one of `unsigned`, `ci-test-key`, `caller-owned`, `notarized` or the exact provider status produced by CI. No unsigned artifact is described as trusted or production-signed.
+
+## Compatibility and upgrade notes
+
+The public package remains `@wenathlan/saddle`. The release does not downgrade the package to `1.8.3`; the active version is `1.8.12`. Version `1.8.21` is reserved for the next objective-driven research and implementation cycle. SignPath Foundation approval and production code-signing credentials remain caller-owned and are not implied by this release note.
+
+## Verification
+
+The prepared state passed 107 active tests, 69 legacy tests, engine build and syntax checks, formatting checks, web TypeScript and Pages build checks, npm pack dry-run, npm audit, flat-native validation and diff hygiene. Final artifact sizes and live download URLs must be filled from the actual GitHub Actions release run rather than estimated in advance.
+
+## References
+
+[1]: https://github.com/wenathlan/saddle "Saddle source repository"
+[2]: https://github.com/wenathlan/saddle/releases "Saddle release archive"
+[3]: https://github.com/wenathlan/saddle/blob/main/LICENSE "Saddle GPL-3.0-only license"

package/docs/releasenotes-1.8.13.md

@@ -0,0 +1,42 @@
+# Saddle 1.8.13
+
+Saddle 1.8.13 carries the active code and release-facing manifests forward from 1.8.12. The previous [1.8.12 release notes](releasenotes-1.8.12.md) remain the canonical record for the licensing and artifact baseline. The comparative 1.8.21 research is planning material and is not presented as a shipped feature.
+
+## Changes
+
+| Area | Change |
+|---|---|
+| Persistent queue | Added caller-owned leases, visibility timeout, deterministic clock injection, renewals, attempt accounting and idempotency-key deduplication. Existing crash recovery and retry behavior remain compatible. |
+| Version identity | Aligned npm, lockfile, Maven, NuGet, RubyGems, browser extension, Tauri, iOS, crawler and Capacitor metadata to `1.8.13`. The iOS marketing version is `1.8.13` with build `1008013`. |
+| Structured extraction | Added a schema-neutral result with field-level source URL, selector, extraction timestamp, bounded UTF-8 payload and caller-injected parser support. |
+| Browser context | Added allowlisted snapshot projection with stable snapshot and element references, deterministic UTF-8 byte budgets and truncation metadata. |
+| Workflow lifecycle | Extended resumable runs with explicit cancellation reasons and caller-owned, idempotent compensation callbacks. Compensation failures are surfaced as `COMPENSATION_FAILED`. |
+| Artifact retention | Added deterministic keep/prune decisions by maximum age, count or bytes. Manifest generation records policy and decisions and never deletes caller files. |
+| Documentation | Added the 1.8.13 release notes and retained the 1.8.12 artifact and signing policy documents. |
+| Architecture | Kept the root-first layout, no project-owned `src` directory, transport-neutral exports and caller-owned infrastructure. |
+
+## Artifact contract
+
+The active workflows derive names from the release tag. The following names are expected for a 1.8.13 run; actual URLs, checksums and sizes must come from the completed CI run.
+
+| Surface | Expected artifact family |
+|---|---|
+| Linux desktop | `saddle.browser.1.8.13.<architecture>.deb`, `.rpm`, `.appimage` |
+| Windows desktop | `saddle.browser.1.8.13.<architecture>.exe`, `.msi` |
+| macOS desktop | `saddle.browser.1.8.13.<architecture>.dmg`, `.app.zip` |
+| Android | `saddle.apk.1.8.13.apk`, `saddle.aab.1.8.13.aab` |
+| iOS | `saddle.ipa.1.8.13.ipa`, `saddle.app.1.8.13.app.zip` |
+| Container | `saddle.container.1.8.13.tar.gz` |
+| Browser extension | `saddle.extension.1.8.13.zip` |
+
+Signing remains explicit. `unsigned`, `ci-test-key`, `caller-owned`, `notarized` and a provider-reported status are distinct states. This release note does not claim SignPath approval or production signing.
+
+## Verification
+
+The queue, structured extraction, browser context, workflow compensation and retention features passed the active engine and release test suites. The complete release gate must be rerun after the implementation commit before a tag or release is created. The 1.8.21 research set remains the planning label for this feature batch and is not presented as a separate published version.
+
+## References
+
+[1]: https://github.com/wenathlan/saddle "Saddle source repository"
+[2]: https://github.com/wenathlan/saddle/releases "Saddle release archive"
+[3]: https://github.com/wenathlan/saddle/blob/main/docs/releasenotes-1.8.12.md "Saddle 1.8.12 release notes"