Skip to content

Refresh the pinned Lync durability boundary - #82

Merged
deepfates merged 1 commit into
mainfrom
codex/textile-lync-durability-refresh
Sep 6, 2026
Merged

Refresh the pinned Lync durability boundary#82
deepfates merged 1 commit into
mainfrom
codex/textile-lync-durability-refresh

Conversation

@deepfates

Copy link
Copy Markdown
Owner

Purpose

Refresh Textile from the earlier unpublished Lync 0.4.3 candidate to the owner-approved clean Lync main commit 828a14017ea71519c510b0808a49d6382a36ed33 (tree f24e6122012f24beea934a1f639117ab15694725). This remains a checksum-pinned local dependency; it does not publish either package. Splice was given the same archive bytes and checksum rather than a repack.

Bounded change

  • replace the old 0a511b6 archive with deepfates-lync-0.4.3-828a140.tgz
  • update package, lockfile, and vendored provenance
  • add one installed-package regression using Lync’s real IndexedDbEventStore with fake-indexeddb mechanics

The regression suspends an archive appendMany, performs Textile-shaped keep/note/cluster mutations through append, union, and appendMany, and opens a fresh store instance after each public operation resolves. Every operation’s own bytes must already be durable. It does not require unrelated operations to wait for the suspended producer.

Evidence

  • archive SHA-256: cc90bfc8766ecab7c7ab53298ca0fdff8e3649626879f6cab7300c071e566196 (192037 bytes)
  • old archive red proof: resolved keep absent after IndexedDB fresh-store reopen while import remained suspended
  • approved archive focused regression: pass
  • approved Lync source: pnpm verify pass, 26 files / 223 tests plus typecheck, examples, and packed-artifact check
  • Textile bun install --frozen-lockfile: pass
  • Textile bun run verify: pass, 229 tests / 1 deliberate scale skip plus lint and production build
  • provider-free ordinary browser path: two authors reconnect, co-curate a Twitter corpus, and reopen portable kept context — pass
  • all 29 installed Lync export subpaths import; additive file-cursor/checkpoint smoke passes
  • git diff --check: pass

These are bounded regression results, not a blanket durability claim.

@deepfates
deepfates temporarily deployed to codex/textile-lync-durability-refresh - textile PR #82 September 6, 2026 21:48 — with Render Destroyed
@deepfates
deepfates merged commit 4cc7e08 into main Sep 6, 2026
1 check passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 50aafae979

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread vendor/LYNC-PROVENANCE.md
# Vendored Lync package

`deepfates-lync-0.4.3-0a511b6.tgz` was produced with `pnpm pack`
`deepfates-lync-0.4.3-828a140.tgz` was produced once with `pnpm pack`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Ship the documents linked from the packed README

When consumers read the README from this vendored package, its primary “Choose your path” links point to docs/library.md, docs/cli.md, docs/relay.md, and docs/architecture.md, but inspection of this exact tarball shows that no package/docs/ files are included. The replacement therefore turns the installed package's main documentation entry points into broken links; include the referenced documentation in the packed files or keep the packed README self-contained.

Useful? React with 👍 / 👎.

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