Skip to content

chore(sdk): refresh byte-pinned mirror to plugin-types@3.0.1 (fn-182.4 mirror order) - #3

Merged
acebytes merged 1 commit into
mainfrom
url-mirror-3.0.1
Aug 14, 2026
Merged

chore(sdk): refresh byte-pinned mirror to plugin-types@3.0.1 (fn-182.4 mirror order)#3
acebytes merged 1 commit into
mainfrom
url-mirror-3.0.1

Conversation

@acebytes

Copy link
Copy Markdown
Contributor

Summary

Completes flow task fn-182.4 (epic fn-182: host-injected Foundation-bridged URL global): the post-publish mandated mirror order, executed after @appos.space/plugin-types@3.0.1 went live on npm (plugin-sdk tag v3.0.1, merge 22dae9a).

Executed exactly as mandated:

  1. npm install --save-dev --save-exact @appos.space/plugin-types@3.0.1 first
  2. then ./scripts/check-sdk-freshness.sh --update
  3. mirror + INDEX.md + .sdk-integrity + package.json + package-lock.json committed together (plus the regenerated compiled/manifest.json)

What changed

  • Mirror (reference/plugin-api/): 10 d.ts files byte-equal to the published 3.0.1 tarball — new globals.d.ts (the opt-in @appos.space/plugin-types/globals subpath declaring the host-injected URL global), index.d.ts docblock teaching the subpath, namespaces.d.ts sheds the stale 2.4.0-fn50 marker, sourceMappingURL trailers now ship in the published d.ts
  • Pins: plugin-types 3.0.0 → 3.0.1 exact, in package.json + lockfile + .sdk-integrity (same sha512 in all three; plugin-utils / view-builders deliberately stay 3.0.0 — the mandate and the freshness gate pin only plugin-types)
  • Compiled factory context: BYTE-IDENTICAL by design — the generator strips JSDoc + sourceMappingURL from mirror files, and globals.d.ts is not a barrel module; only manifest source hashes moved (179187 ≤ 179200 ceiling). Desktop-side Sources/TwoPanez/Resources/ writes reverted — fn-182.5 owns those.

Gates

  • npm run check exit 0: check-sdk-freshness (Gate 0 coherence + 10 files byte-equal + integrity match) · verify-knowledge (69 fences green against the 3.0.1 package; hardened fail-closed parsers accepted the new d.ts) · check-compiled-freshness (2 artifacts, 12 sources fresh)
  • codex impl-review (base 2598cf2): SHIP round 1

The pre-publish half of fn-182.4 (verifier URL env, scaffold fence, patterns §24, teaching-doc rewording) already landed via PR #2 (f9bb2ea + review rounds), codex-SHIPped separately.

….0.1

Mandated order (fn-182.4): exact-pin npm install FIRST, then
check-sdk-freshness --update, committed together:
- package.json + package-lock.json: plugin-types 3.0.0 -> 3.0.1 (exact)
- .sdk-integrity: 3.0.1 + tarball sha512
- reference/plugin-api/ mirror: 10 d.ts files byte-equal to the 3.0.1
  tarball — NEW globals.d.ts (opt-in /globals subpath declaring the
  host-injected URL global), index.d.ts docblock teaches the subpath,
  namespaces.d.ts sheds the stale 2.4.0-fn50 @Version marker,
  sourceMappingURL trailers now ship in the published d.ts
- INDEX.md regenerated (10 modules)
- compiled/manifest.json: refreshed source hashes only — the compiled
  factory context is BYTE-IDENTICAL (generator strips JSDoc +
  sourceMappingURL, absorbing every mirror text change; 179187 <= 179200
  ceiling; Desktop-side generator writes reverted — task fn-182.5 owns
  those)

Gates: npm run check exit 0 (mirror byte-equal, verify-knowledge 69
fences green, compiled-freshness 2 artifacts + 12 sources fresh).

Task: fn-182-inject-foundation-bridged-url-global.4
@acebytes
acebytes merged commit a3446bb into main Aug 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant