Skip to content

chore(napi): bump fluessig pin to e056bb9 (#74/#77/#80)#332

Draft
zmaril wants to merge 1 commit into
napi-fluessig/trust-managerfrom
napi-fluessig/fluessig-pin-e056bb9
Draft

chore(napi): bump fluessig pin to e056bb9 (#74/#77/#80)#332
zmaril wants to merge 1 commit into
napi-fluessig/trust-managerfrom
napi-fluessig/fluessig-pin-e056bb9

Conversation

@zmaril

@zmaril zmaril commented Jul 21, 2026

Copy link
Copy Markdown
Owner

Bumps the fluessig pin from 1fed77a to fluessig main HEAD e056bb966240be297cc9c60a32cf99436a54801f, which combines:

Changes

Pin refs only (6 files):

  • crates/pidgin-napi/Cargo.tomlfluessig-runtime git-dep rev
  • crates/pidgin-napi/regen.shpinned_rev + comment
  • Cargo.lockfluessig-runtime source
  • bindings/php/Cargo.tomlfluessig-runtime git-dep rev
  • bindings/php/regen.shpinned_rev + comment
  • bindings/php/Cargo.lockfluessig-runtime source

Byte-stability gate (the point of this bump)

Re-ran both regen scripts against the new pin and rebuilt the napi addon before and after the bump:

  • crates/pidgin-napi/src/generated.rsbyte-identical (git clean after node regen)
  • bindings/php/src/generated.rsbyte-identical (git clean after PHP regen)
  • napi addon index.d.tsbyte-identical (sha match, diff empty)
  • napi addon index.jsbyte-identical (sha match, diff empty)

None of the ~17 already-generated modules use float/bytes/single_threaded, so #74/#77/#80 do not alter their output. The only tree changes are the pin refs themselves.

Checks

  • cargo build -p pidgin-napi — clean
  • cargo fmt --all --check — clean
  • cargo clippy -p pidgin-napi --all-targets -- -D warnings — clean
  • codespell — 0
  • straitjacket v0.2.3 on git archive HEAD — 0 errors

Generated by Claude Code

Bump the fluessig pin from 1fed77a to fluessig main HEAD
e056bb966240be297cc9c60a32cf99436a54801f, which combines #74
(bytes/envelope), #77 (float/uint scalar arms), and #80
(single_threaded). Bumps the fluessig-runtime git-dep rev and the
regen.sh pinned_rev on both the node (crates/pidgin-napi) and PHP
(bindings/php) sides, plus both Cargo.lock entries.

Byte-stability verified: re-running both regen scripts against the new
pin leaves src/generated.rs byte-identical on both sides, and the napi
addon's index.d.ts / index.js are byte-identical before and after the
bump. None of the ~17 already-generated modules use float/bytes/
single_threaded, so #74/#77/#80 do not alter their output.
@github-actions

Copy link
Copy Markdown

Conformance smoke: agent + ai + tui

  • pi_sha: 3da591ab74ab9ab407e72ed882600b2c851fae21
  • manifest_native_modules: 45

Headline is rust-backed: passing cases in files whose module-under-test is a native (Rust addon) module. Raw all-pass is shown secondary — it is inflated by unflipped TypeScript that passes without touching any Rust.

Package rust-backed Native modules raw pass (secondary) Failing Skipped
agent 55/180 (30.6%) 5 180/180 0 0
ai 74/1295 (5.7%) 8 553/1295 3 739
tui 375/678 (55.3%) 14 678/678 0 0
smoke total 504/2153 (23.4%) 27 1411/2153 3 739

agent: 55/180 (30.6%) · ai: 74/1295 (5.7%) · tui: 375/678 (55.3%)

rust-backed = passing / total tests run, per the manifest's per-native-row tests lists. The Native modules column counts modules served by the Rust addon. This is the agent+ai+tui smoke subset; the full baseline lives in committed conformance.json.

Attribution

A pi test file is rust-backed iff the module it primarily exercises — its module-under-test — is status=native in conformance/manifest.json. A package's rust-backed count is the passing cases in its rust-backed files. Transitive or infrastructure use does not count (e.g. ~30 ai files construct the native faux provider but test other things — only faux-provider.test.ts, whose subject is faux, counts). A file that substantially tests both a native and an original module is excluded rather than counted, so the number under-reports rather than over-claims.

Per-file decisions (from each native manifest row's tests list):

Native module Test file Decision
ai/api/anthropic-messages.ts test/anthropic-sse-parsing.test.ts counted
ai/providers/faux.ts test/faux-provider.test.ts counted
coding-agent/utils/ansi.ts test/ansi-utils.test.ts counted
coding-agent/utils/changelog.ts test/changelog.test.ts counted
coding-agent/utils/git.ts test/git-ssh-url.test.ts counted
coding-agent/core/tools/path-utils.ts test/path-utils.test.ts counted
tui/keys.ts test/keys.test.ts counted
tui/utils.ts test/truncate-to-width.test.ts, test/regression-regional-indicator-width.test.ts counted
coding-agent/utils/mime.ts test/image-process.test.ts mixed — excluded (2 of 3 cases test processImage/original)
coding-agent/utils/version-check.ts test/version-check.test.ts mixed — excluded (fetch cases mock the original; not separable per-file)
coding-agent/core/export-html/ansi-to-html.ts test/export-html-whitespace.test.ts mixed — excluded (asset-grep + tool-renderer/original dominate)
coding-agent/core/tools/truncate.ts no dedicated test (exercised via tools.test.ts, subject is the read/edit factory/original)
coding-agent/core/tools/edit-diff.ts no dedicated test (edit-tool tests' subject is the edit tool/original)

CLI conformance (black-box, against the pidgin binary)

  • CLI conformance: 15/15 pass against target/release/pidgin (pass delta ±0, fail delta ±0).
File Passing Failing Skipped
packages/coding-agent/test/session-file-invalid.test.ts 1 0 0
packages/coding-agent/test/session-id-readonly.test.ts 7 0 0
packages/coding-agent/test/startup-session-name.test.ts 2 0 0
packages/coding-agent/test/stdout-cleanliness.test.ts 5 0 0

The four repointed coding-agent CLI test files spawn the compiled pidgin binary via $PIDGIN_BIN instead of pi's own cli.ts. This is a separate signal from the module smoke table and is never folded into the per-package Native count.

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.

2 participants