Documented release
v113.5.0
clean stabilization
Release date 2026-07-26
Outcome
Outcome
The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
Changes
What changed
Offline Studio can Record and Seal without requiring a Receiz…
Offline Studio can Record and Seal without requiring a Receiz identity while still using canonical Signature V4 proof mechanics.
Technical and authority boundary
Offline Studio can Record and Seal without requiring a Receiz identity while still using canonical Signature V4 proof mechanics.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Offline Studio can Record and Seal without requiring a Receiz identity while still using canonical Signature V4 proof mechanics.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Device signing moved to local-first enrollment with canonical server enrollment…
Device signing moved to local-first enrollment with canonical server enrollment, fixed certificate expiry, and optional authenticated ownership.
Technical and authority boundary
Device signing moved to local-first enrollment with canonical server enrollment, fixed certificate expiry, and optional authenticated ownership.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Device signing moved to local-first enrollment with canonical server enrollment, fixed certificate expiry, and optional authenticated ownership.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Record/Seal no longer redirects through sign-in or leaves the surface half-provisioned
Record/Seal no longer redirects through sign-in or leaves the surface half-provisioned.
Technical and authority boundary
Record/Seal no longer redirects through sign-in or leaves the surface half-provisioned.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Record/Seal no longer redirects through sign-in or leaves the surface half-provisioned.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Trailer-sealed image bytes, source format, download MIME, and exact-file download/share…
Trailer-sealed image bytes, source format, download MIME, and exact-file download/share behavior are preserved.
Technical and authority boundary
Trailer-sealed image bytes, source format, download MIME, and exact-file download/share behavior are preserved.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Trailer-sealed image bytes, source format, download MIME, and exact-file download/share behavior are preserved.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
PNG bases exclude mutable provenance and anchor chunks before sealing
PNG bases exclude mutable provenance and anchor chunks before sealing.
Technical and authority boundary
PNG bases exclude mutable provenance and anchor chunks before sealing.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- PNG bases exclude mutable provenance and anchor chunks before sealing.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
The standalone offline proof instruments remain exact and independently usable
The standalone offline proof instruments remain exact and independently usable. Why: an offline proof object must remain the same sealed artifact across save, share, camera-roll handling, download, and later verification. Identity/session mechanics cannot outrank or rewrite the artifact. JPEG and HEIC proof carriers survive real iOS Photos transformations
Technical and authority boundary
The standalone offline proof instruments remain exact and independently usable. Why: an offline proof object must remain the same sealed artifact across save, share, camera-roll handling, download, and later verification. Identity/session mechanics cannot outrank or rewrite the artifact. JPEG and HEIC proof carriers survive real iOS Photos transformations
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- The standalone offline proof instruments remain exact and independently usable. Why: an offline proof object must remain the same sealed artifact across save, share, camera-roll handling, download, and later verification. Identity/session mechanics cannot outrank or rewrite the artifact. JPEG and HEIC proof carriers survive real iOS Photos transformations
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
JPEG XMP-normalized artifact binding was added and frozen by contract
JPEG XMP-normalized artifact binding was added and frozen by contract.
Technical and authority boundary
JPEG XMP-normalized artifact binding was added and frozen by contract.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- JPEG XMP-normalized artifact binding was added and frozen by contract.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
The JPEG carrier advanced through fail-closed IFD1 v3, iOS Photos…
The JPEG carrier advanced through fail-closed IFD1 v3, iOS Photos normalization, MakerNote v4, v5 basis handling, and v6 rational canonicalization.
Technical and authority boundary
The JPEG carrier advanced through fail-closed IFD1 v3, iOS Photos normalization, MakerNote v4, v5 basis handling, and v6 rational canonicalization.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- The JPEG carrier advanced through fail-closed IFD1 v3, iOS Photos normalization, MakerNote v4, v5 basis handling, and v6 rational canonicalization.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Native HEIC proof objects gained file detection, a canonical UUID…
Native HEIC proof objects gained file detection, a canonical UUID proof channel, Record/Seal creation, camera-roll-safe saving, offline verification, and UI projection.
Technical and authority boundary
Native HEIC proof objects gained file detection, a canonical UUID proof channel, Record/Seal creation, camera-roll-safe saving, offline verification, and UI projection.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Native HEIC proof objects gained file detection, a canonical UUID proof channel, Record/Seal creation, camera-roll-safe saving, offline verification, and UI projection.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
iPhone PWA save behavior now uses the exact-file download surface…
iPhone PWA save behavior now uses the exact-file download surface and native file sharing where available.
Technical and authority boundary
iPhone PWA save behavior now uses the exact-file download surface and native file sharing where available.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- iPhone PWA save behavior now uses the exact-file download surface and native file sharing where available.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Simulated iOS Photos transformations and first-save evidence are locked into…
Simulated iOS Photos transformations and first-save evidence are locked into regression coverage. Why: Photos applications may rewrite container metadata without changing the human-visible media. Receiz must recompute the permitted canonical basis, reject unsupported mutations, and preserve the proof object’s deterministic identity without relying on a server. Verify is proof-native and useful in airplane mode
Technical and authority boundary
Simulated iOS Photos transformations and first-save evidence are locked into regression coverage. Why: Photos applications may rewrite container metadata without changing the human-visible media. Receiz must recompute the permitted canonical basis, reject unsupported mutations, and preserve the proof object’s deterministic identity without relying on a server. Verify is proof-native and useful in airplane mode
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Simulated iOS Photos transformations and first-save evidence are locked into regression coverage. Why: Photos applications may rewrite container metadata without changing the human-visible media. Receiz must recompute the permitted canonical basis, reject unsupported mutations, and preserve the proof object’s deterministic identity without relying on a server. Verify is proof-native and useful in airplane mode
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
/verify now verifies local proof objects before network, session, append…
/verify now verifies local proof objects before network, session, append, or server work.
Technical and authority boundary
/verify now verifies local proof objects before network, session, append, or server work.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- /verify now verifies local proof objects before network, session, append, or server work.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
The installed PWA and standalone verifiers preserve offline verification for…
The installed PWA and standalone verifiers preserve offline verification for JPEG, HEIC, and existing sealed proof carriers.
Technical and authority boundary
The installed PWA and standalone verifiers preserve offline verification for JPEG, HEIC, and existing sealed proof carriers.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- The installed PWA and standalone verifiers preserve offline verification for JPEG, HEIC, and existing sealed proof carriers.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Optional append work is isolated in a durable outbox and…
Optional append work is isolated in a durable outbox and cannot change the local verification verdict.
Technical and authority boundary
Optional append work is isolated in a durable outbox and cannot change the local verification verdict.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Optional append work is isolated in a durable outbox and cannot change the local verification verdict.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
The service worker preserves exact offline proof instruments and avoids…
The service worker preserves exact offline proof instruments and avoids fake loading or network-first rediscovery of known proof truth. Why: offline verification is the primitive, not a fallback. A valid sealed proof object must verify by recomputation from its own bytes; later appends may enrich history only after the verdict is settled. Signed upload and public-proof continuity edge cases were closed
Technical and authority boundary
The service worker preserves exact offline proof instruments and avoids fake loading or network-first rediscovery of known proof truth. Why: offline verification is the primitive, not a fallback. A valid sealed proof object must verify by recomputation from its own bytes; later appends may enrich history only after the verdict is settled. Signed upload and public-proof continuity edge cases were closed
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- The service worker preserves exact offline proof instruments and avoids fake loading or network-first rediscovery of known proof truth. Why: offline verification is the primitive, not a fallback. A valid sealed proof object must verify by recomputation from its own bytes; later appends may enrich history only after the verdict is settled. Signed upload and public-proof continuity edge cases were closed
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Interrupted signed uploads can retry without losing the prepared proof object
Interrupted signed uploads can retry without losing the prepared proof object.
Technical and authority boundary
Interrupted signed uploads can retry without losing the prepared proof object.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Interrupted signed uploads can retry without losing the prepared proof object.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Lagging public projections cannot overwrite stronger prepared or locally held…
Lagging public projections cannot overwrite stronger prepared or locally held proof truth.
Technical and authority boundary
Lagging public projections cannot overwrite stronger prepared or locally held proof truth.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Lagging public projections cannot overwrite stronger prepared or locally held proof truth.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Profile visibility queries are bounded, saved proofs are defended, and…
Profile visibility queries are bounded, saved proofs are defended, and global publish/sync contracts protect the completed proof object.
Technical and authority boundary
Profile visibility queries are bounded, saved proofs are defended, and global publish/sync contracts protect the completed proof object.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Profile visibility queries are bounded, saved proofs are defended, and global publish/sync contracts protect the completed proof object.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
PBI authorship no longer depends on a generic anchor-verification prerequisite
PBI authorship no longer depends on a generic anchor-verification prerequisite. Why: server rows, partial public projections, and retry state are weaker than the sealed or prepared proof object. They may index or append beneath it but cannot erase or downgrade it. Sports reward closeout is atomic under pressure
Technical and authority boundary
PBI authorship no longer depends on a generic anchor-verification prerequisite. Why: server rows, partial public projections, and retry state are weaker than the sealed or prepared proof object. They may index or append beneath it but cannot erase or downgrade it. Sports reward closeout is atomic under pressure
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- PBI authorship no longer depends on a generic anchor-verification prerequisite. Why: server rows, partial public projections, and retry state are weaker than the sealed or prepared proof object. They may index or append beneath it but cannot erase or downgrade it. Sports reward closeout is atomic under pressure
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Sports reward closeout gained a durable queue, explicit atomic closeout…
Sports reward closeout gained a durable queue, explicit atomic closeout behavior, backpressure handling, worker routing, and focused tests.
Technical and authority boundary
Sports reward closeout gained a durable queue, explicit atomic closeout behavior, backpressure handling, worker routing, and focused tests.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Sports reward closeout gained a durable queue, explicit atomic closeout behavior, backpressure handling, worker routing, and focused tests.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Main Event / arena settlement cannot double-close or silently lose…
Main Event / arena settlement cannot double-close or silently lose reward completion when concurrent work or retries occur.
Technical and authority boundary
Main Event / arena settlement cannot double-close or silently lose reward completion when concurrent work or retries occur.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Main Event / arena settlement cannot double-close or silently lose reward completion when concurrent work or retries occur.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Pitch Command’s completed archive window and packaged day-proof evidence were…
Pitch Command’s completed archive window and packaged day-proof evidence were brought current. Why: reward closeout is a settlement primitive. A completed reward must have one durable terminal state; retries and worker pressure cannot manufacture a second settlement or reopen a settled one. Deterministic first paint and release quality were tightened
Technical and authority boundary
Pitch Command’s completed archive window and packaged day-proof evidence were brought current. Why: reward closeout is a settlement primitive. A completed reward must have one durable terminal state; retries and worker pressure cannot manufacture a second settlement or reopen a settled one. Deterministic first paint and release quality were tightened
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Pitch Command’s completed archive window and packaged day-proof evidence were brought current. Why: reward closeout is a settlement primitive. A completed reward must have one durable terminal state; retries and worker pressure cannot manufacture a second settlement or reopen a settled one. Deterministic first paint and release quality were tightened
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
First-paint typography is locked across Safari and installed PWAs
First-paint typography is locked across Safari and installed PWAs.
Technical and authority boundary
First-paint typography is locked across Safari and installed PWAs.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- First-paint typography is locked across Safari and installed PWAs.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Service-worker and offline-studio release identities advance together to invalidate old…
Service-worker and offline-studio release identities advance together to invalidate old runtime shells without changing settled product logic.
Technical and authority boundary
Service-worker and offline-studio release identities advance together to invalidate old runtime shells without changing settled product logic.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Service-worker and offline-studio release identities advance together to invalidate old runtime shells without changing settled product logic.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
The standalone Offline Studio file targets now render as full-width…
The standalone Offline Studio file targets now render as full-width drop surfaces instead of collapsing as inline labels; a frozen contract prevents recurrence.
Technical and authority boundary
The standalone Offline Studio file targets now render as full-width drop surfaces instead of collapsing as inline labels; a frozen contract prevents recurrence.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- The standalone Offline Studio file targets now render as full-width drop surfaces instead of collapsing as inline labels; a frozen contract prevents recurrence.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Lint now completes with zero warnings
Lint now completes with zero warnings. Cleanup was limited to unused imports, unused dead helpers, an unused function parameter, and an underscore convention for intentionally discarded test bindings. Why: a clean release must identify the exact shipped runtime, preserve deterministic first paint, and contain no warning noise that could hide a later regression.
Technical and authority boundary
Lint now completes with zero warnings. Cleanup was limited to unused imports, unused dead helpers, an unused function parameter, and an underscore convention for intentionally discarded test bindings. Why: a clean release must identify the exact shipped runtime, preserve deterministic first paint, and contain no warning noise that could hide a later regression.
- Why
- The public package surface is @receiz/sdk. Durable proof memory remains first admission only, then append forever.
- Capability enabled
- Lint now completes with zero warnings. Cleanup was limited to unused imports, unused dead helpers, an unused function parameter, and an underscore convention for intentionally discarded test bindings. Why: a clean release must identify the exact shipped runtime, preserve deterministic first paint, and contain no warning noise that could hide a later regression.
- Compatibility
- The v113.5.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v113.5.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
The frozen v113 ruleset, constitution registry, artifact-law version, application operation matrix, compiler target, and SDK/MCP compatibility interval remain v113.0.0 / =113.0.0 <114.0.0. This patch release does not invent a v113.5 authority layer and does not absorb v114 work.
Available outcomes
Capabilities now available
Offline Studio can Record and Seal without requiring a Receiz…
Offline Studio can Record and Seal without requiring a Receiz identity while still using canonical Signature V4 proof mechanics.
Device signing moved to local-first enrollment with canonical server enrollment…
Device signing moved to local-first enrollment with canonical server enrollment, fixed certificate expiry, and optional authenticated ownership.
Record/Seal no longer redirects through sign-in or leaves the surface half-provisioned
Record/Seal no longer redirects through sign-in or leaves the surface half-provisioned.
Trailer-sealed image bytes, source format, download MIME, and exact-file download/share…
Trailer-sealed image bytes, source format, download MIME, and exact-file download/share behavior are preserved.
PNG bases exclude mutable provenance and anchor chunks before sealing
PNG bases exclude mutable provenance and anchor chunks before sealing.
The standalone offline proof instruments remain exact and independently usable
The standalone offline proof instruments remain exact and independently usable. Why: an offline proof object must remain the same sealed artifact across save, share, camera-roll handling, download, and later verification. Identity/session mechanics cannot outrank or rewrite the artifact. JPEG and HEIC proof carriers survive real iOS Photos transformations
JPEG XMP-normalized artifact binding was added and frozen by contract
JPEG XMP-normalized artifact binding was added and frozen by contract.
The JPEG carrier advanced through fail-closed IFD1 v3, iOS Photos…
The JPEG carrier advanced through fail-closed IFD1 v3, iOS Photos normalization, MakerNote v4, v5 basis handling, and v6 rational canonicalization.
Native HEIC proof objects gained file detection, a canonical UUID…
Native HEIC proof objects gained file detection, a canonical UUID proof channel, Record/Seal creation, camera-roll-safe saving, offline verification, and UI projection.
iPhone PWA save behavior now uses the exact-file download surface…
iPhone PWA save behavior now uses the exact-file download surface and native file sharing where available.
Simulated iOS Photos transformations and first-save evidence are locked into…
Simulated iOS Photos transformations and first-save evidence are locked into regression coverage. Why: Photos applications may rewrite container metadata without changing the human-visible media. Receiz must recompute the permitted canonical basis, reject unsupported mutations, and preserve the proof object’s deterministic identity without relying on a server. Verify is proof-native and useful in airplane mode
/verify now verifies local proof objects before network, session, append…
/verify now verifies local proof objects before network, session, append, or server work.
The installed PWA and standalone verifiers preserve offline verification for…
The installed PWA and standalone verifiers preserve offline verification for JPEG, HEIC, and existing sealed proof carriers.
Optional append work is isolated in a durable outbox and…
Optional append work is isolated in a durable outbox and cannot change the local verification verdict.
The service worker preserves exact offline proof instruments and avoids…
The service worker preserves exact offline proof instruments and avoids fake loading or network-first rediscovery of known proof truth. Why: offline verification is the primitive, not a fallback. A valid sealed proof object must verify by recomputation from its own bytes; later appends may enrich history only after the verdict is settled. Signed upload and public-proof continuity edge cases were closed
Interrupted signed uploads can retry without losing the prepared proof object
Interrupted signed uploads can retry without losing the prepared proof object.
Lagging public projections cannot overwrite stronger prepared or locally held…
Lagging public projections cannot overwrite stronger prepared or locally held proof truth.
Profile visibility queries are bounded, saved proofs are defended, and…
Profile visibility queries are bounded, saved proofs are defended, and global publish/sync contracts protect the completed proof object.
PBI authorship no longer depends on a generic anchor-verification prerequisite
PBI authorship no longer depends on a generic anchor-verification prerequisite. Why: server rows, partial public projections, and retry state are weaker than the sealed or prepared proof object. They may index or append beneath it but cannot erase or downgrade it. Sports reward closeout is atomic under pressure
Sports reward closeout gained a durable queue, explicit atomic closeout…
Sports reward closeout gained a durable queue, explicit atomic closeout behavior, backpressure handling, worker routing, and focused tests.
Main Event / arena settlement cannot double-close or silently lose…
Main Event / arena settlement cannot double-close or silently lose reward completion when concurrent work or retries occur.
Pitch Command’s completed archive window and packaged day-proof evidence were…
Pitch Command’s completed archive window and packaged day-proof evidence were brought current. Why: reward closeout is a settlement primitive. A completed reward must have one durable terminal state; retries and worker pressure cannot manufacture a second settlement or reopen a settled one. Deterministic first paint and release quality were tightened
First-paint typography is locked across Safari and installed PWAs
First-paint typography is locked across Safari and installed PWAs.
Service-worker and offline-studio release identities advance together to invalidate old…
Service-worker and offline-studio release identities advance together to invalidate old runtime shells without changing settled product logic.
The standalone Offline Studio file targets now render as full-width…
The standalone Offline Studio file targets now render as full-width drop surfaces instead of collapsing as inline labels; a frozen contract prevents recurrence.
Lint now completes with zero warnings
Lint now completes with zero warnings. Cleanup was limited to unused imports, unused dead helpers, an unused function parameter, and an underscore convention for intentionally discarded test bindings. Why: a clean release must identify the exact shipped runtime, preserve deterministic first paint, and contain no warning noise that could hide a later regression.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- settlement
- provenance
- media
- verification
- public-witness
- local-truth
- continuity
- certificate
- sealed-artifact
Compatibility
Compatibility
Archive compatibility evidence boundary
No dedicated compatibility record is bound to this projection.
Treat compatibility as unknown; version or date proximity is not evidence.
Migration
Migration
Required: unknown
No explicit migration source is bound; no migration is inferred from dates.
Qualification
Conformance
pnpm lint reports zero warnings and zero errors
Passed · pnpm lint reports zero warnings and zero errors
Governance checks pass
Passed · Governance checks pass
Full pnpm test:release-freeze passes from the exact release tree
Passed · Full pnpm test:release-freeze passes from the exact release tree
Control boundary
Governance
- Verification
- Passed
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Governance verification passed against the exact checked release evidence bound below.
No separate release approval reference or risk-owner assignment is inferred from conformance evidence.
Registry boundary
Registry
No registry is bound where the canonical release family does not carry one.
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- proof · identity · ownership · settlement · provenance · media · verification · public-witness · local-truth · continuity · certificate · sealed-artifact
- Change kinds
- capability
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Unknown
- Deployment
- Not Performed
- Production smoke
- Unknown
- Signed attestation
- Absent
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 0cf385484df9eb55884cd822722dc4741ba96088c55411600994189529d34b25. Source-family inventory: complete.
SHA-256 0369be4dade050329d3c4df9d3f50c868c64f8ba47734db94e4e4b55e1be2a31SHA-256 4e43de15214d2c0c4329181cf3c44f43e49c15b8c0597823debf601ca24d894fSHA-256 62bd4baeeaf11168eb16471f61c58c583319c80eb82a8ffe74f32be87d2b0913SHA-256 3c9b6c5ce48b17a183e729d7a4357ef658a2c8babe8433a7053f3906e916c7c5SHA-256 afa4e3af1126d43f02b8a444fee34eecd8faa88ae0fd87d1fffa180e8edaa857SHA-256 0fcfda654573bf1857cc48fa29bbdefc97d47e9e0af287af3911e6eefb5369c5SHA-256 508331cefccdd1b2381309816e921a5c836b0a924c41c72d61f0503b3ed885c0