[Bug] Released archives omit amazon-bedrock.js, blocking Bedrock and Homebrew

[fettpl]

Affected area

Release packaging, coding agent and CLI

What happened?

The published Prime Agent archives for v0.7.0, v0.7.1, and v0.7.2 omit dist/bundle/amazon-bedrock.js, although a generated bundle chunk still loads it with:

importNodeOnlyProvider("./amazon-bedrock.js")

Any Bedrock request therefore fails with Cannot find module .../dist/bundle/amazon-bedrock.js. This can also break users who did not explicitly select Bedrock: with no provider configured, the presence of an AWS credential environment variable such as AWS_PROFILE can auto-detect Bedrock during startup.

The v0.7.2 GitHub and R2 archives are byte-identical (sha256:bc5471f2a626d727b88a45eb745fff93b10c554a3c4fc5912f25d8c64b987f5e) and both have the missing entry. The problem has been independently reproduced on macOS and Windows.

Root cause and existing fix

importNodeOnlyProvider(specifier) makes the import target dynamic from esbuild's perspective, so esbuild neither emits nor rewrites the Bedrock provider entry. A clean rebuild of the same source does not fix the artifact.

Closed PR #860 contains a focused source fix at commit 36842d0:

• add amazon-bedrock as an explicit esbuild entry;
• keep the existing lazy node-only loading path; and
• fail the bundle step when a referenced node-only provider asset was not emitted.

The PR and original bug #751 were closed during the issue/PR queue migration, not because the released artifact was corrected. I am re-filing here under the new discussion-first process.

Homebrew impact

This is the remaining Prime Agent release blocker for the existing official submission Homebrew/homebrew-core#297372. The other upstream requirements are complete:

• the Homebrew-owned updater behavior shipped in v0.7.2 via fix(coding-agent): preserve Homebrew update ownership #846; and
• shared system-libzmq support shipped as zeromq@6.6.0 via fix: restore shared libzmq builds zeromq/zeromq.js#737.

The Homebrew formula should not move to v0.7.2 because it would still ship a broken provider.

Expected resolution and verification

1. Land the fix(coding-agent): include Bedrock in Node bundle #860 fix, either from the existing commit or a maintainer-owned implementation.
2. Publish a new stable release rather than replacing an existing artifact.
3. Verify the published archive contains dist/bundle/amazon-bedrock.js.
4. Import that emitted module and confirm it exports streamBedrock and streamSimpleBedrock.
5. Confirm the GitHub and R2 artifacts are immutable and byte-identical.
6. Update and validate the existing Homebrew PR against that release and zeromq@6.6.0.

@badlogic @kevinjosethomas could you accept this into the maintainer work queue and either invite the existing patch or apply the focused fix internally? The historical end-to-end packaging record is #843.

[galsapir]

Confirmed this persists in the official 0.7.3 install on Linux / Node 22. chunk-SOOXXJ56.js references ./amazon-bedrock.js, but the file is absent from dist/bundle, and first inference fails with ERR_MODULE_NOT_FOUND.

I reproduced it with EC2 role credentials and amazon-bedrock/global.openai.gpt-5.6-sol. This local shim restores the expected exports:

import { bedrockProviderModule } from "@earendil-works/pi-ai/bedrock-provider";
export const { streamBedrock, streamSimpleBedrock } = bedrockProviderModule;

After adding it, real calls to both global.openai.gpt-5.6-sol and us.anthropic.claude-sonnet-4-6 succeeded with OpenAI/Anthropic API-key environment variables removed. So the published 0.7.3 artifact still needs the explicit Bedrock bundle entry described above.

[fettpl]

Status delta — 2026-08-20

• Prime Agent v0.7.4 was published from af0b8e00. I inspected the official prime-agent-0.7.4.tgz (sha256:dea045d7c170466a102e030e940f459cc13f2c113465f40be1c7505d80405d2e): it still omits dist/bundle/amazon-bedrock.js, while chunk-XJRALBD3.js still calls importNodeOnlyProvider("./amazon-bedrock.js"). The release therefore does not resolve this defect.
• Independent Linux/Node 22 reproduction also confirms the same failure in v0.7.3 and successful real Bedrock calls after supplying the missing module.
• Homebrew/homebrew-core#297372 remains open and unchanged at v0.7.0 (79b78481), so no duplicate submission or formula update is appropriate yet. zeromq@6.6.0 remains ready; the corrected Prime Agent release is still the only upstream blocker.

@badlogic @kevinjosethomas please accept this into the maintainer work queue and either implement the explicit Bedrock bundle entry plus emitted-asset validation, or invite the focused patch previously available in #860. @kennethnym should keep the existing Homebrew PR on hold until a corrected release archive passes artifact verification.

[fettpl]

Status delta — 2026-08-22

• Prime Agent v0.8.0 was published from 8d7deeab. I inspected the official prime-agent-0.8.0.tgz (sha256:f5b0093c7e0fddb73f94773d74383585456adfa84f12a4082d3098f23bb8fab6): it still omits dist/bundle/amazon-bedrock.js, while chunk-RAPHIPVY.js still imports ./amazon-bedrock.js. The Bedrock defect therefore persists in v0.8.0.
• No maintainer-created replacement issue or invited fix PR exists for this defect. The focused fix in fix(coding-agent): include Bedrock in Node bundle #860 remains closed without merge.
• Homebrew/homebrew-core#297372 remains open and unchanged at v0.7.0 (79b78481). Its released zeromq@6.6.0 dependency is ready; the missing Bedrock bundle in Prime Agent remains the upstream blocker.

@badlogic @kevinjosethomas please accept this defect into the maintainer work queue and either implement the explicit Bedrock entry plus emitted-asset validation or invite the focused #860 patch. @kennethnym should keep the existing Homebrew PR on hold until a corrected stable archive passes artifact verification.

[fettpl]

Status delta — 2026-08-26

• Prime Agent v0.8.1 was published from 51463372. I inspected the official prime-agent-0.8.1.tgz (sha256:46c24db1782dd31adc35d5c6cbcc75564faba6ced3bf2ccf03d836ee77134475): it still omits dist/bundle/amazon-bedrock.js, while chunk-OKDNBPEN.js still calls importNodeOnlyProvider("./amazon-bedrock.js"). The release remains blocked for Homebrew.
• @kaluli123123 independently reproduced the defect on current main, documented a tested fix in Discussion #1763, and submitted PR #1784. The PR adds the explicit Bedrock esbuild entry plus post-build closure validation, matching the previously closed fix(coding-agent): include Bedrock in Node bundle #860 approach.
• fix(coding-agent): close the Amazon Bedrock chunk in the release bundle #1784 was automatically closed because its author is not vouched, not because the fix was rejected on technical review. It has no review or CI result beyond the contribution gate. Homebrew/homebrew-core#297372 remains open and unchanged at v0.7.0.

@badlogic @kevinjosethomas please accept the defect into the maintainer work queue and either vouch/invite @kaluli123123 to resubmit #1784 or apply its focused commit internally. @kennethnym should keep the existing Homebrew PR on hold until a corrected stable archive passes artifact verification.

[kaluli123123]

I understand the contribution gate and will not keep reopening PRs until a maintainer invites the implementation or vouches this account.

For the Bedrock release-bundle issue, I updated the focused fix on my fork at 7acfae7b721d8e00ef3f1c3779767c44d05fc09b.

Validation:

• npm --prefix packages/coding-agent run bundle exits 0.
• dist/bundle/amazon-bedrock.js is emitted.
• Importing it exposes both runtime exports: streamBedrock and streamSimpleBedrock.
• npm run check exits 0.

Could a maintainer advise whether you prefer to:

1. invite a PR from this account,
2. vouch this account for this contribution, or
3. cherry-pick the commit into a maintainer-owned branch?

[fettpl]

Status delta — 2026-08-28

• @kaluli123123 updated the focused Bedrock fix to 7acfae7b. The revised validation confirms amazon-bedrock.js is emitted, exports both streamBedrock and streamSimpleBedrock, and passes npm run check.
• PR #1874 carrying that revision was automatically closed by the non-vouched contributor gate before technical review or CI. Discussion #1763 now explicitly requests a maintainer invitation, vouch, or internal application of the commit.
• Prime Agent v0.8.1 remains the latest verified release and still lacks the Bedrock module. Homebrew/homebrew-core#297372 remains open and unchanged at v0.7.0.

@badlogic @kevinjosethomas please choose an allowed contribution path for 7acfae7b. @kennethnym should keep the existing Homebrew PR on hold until the fix ships in a stable archive and passes artifact verification.

[fettpl]

Status delta — 2026-08-29

• Homebrew/homebrew-core#297372 was automatically marked stale and at risk of closure. I confirmed the submission remains active, linked this coordination record and the validated Bedrock fix, and asked @kennethnym to keep the existing PR open. No duplicate submission was created.
• Prime Agent v0.8.1 remains the latest release and still lacks dist/bundle/amazon-bedrock.js. The source fix at 7acfae7b remains validated but cannot enter review until maintainers select an allowed contribution path.

@badlogic @kevinjosethomas please invite/vouch the contributor or apply 7acfae7b internally so a corrected stable archive can unblock the preserved Homebrew PR.

[fettpl]

Status delta — 2026-09-01

• Independent v0.8.1 testing confirms the released archive still fails at first Bedrock use and adds an important acceptance detail: bundling the package's wrapper entry alone exposes bedrockProviderModule, not the top-level streamBedrock and streamSimpleBedrock names expected by register-builtins.ts.
• The current 7acfae7b patch already addresses that detail by using dist/providers/amazon-bedrock.js as the explicit entry. Its emitted module exposes both expected functions, and independent testing confirms that this direct-provider entry completes a real Bedrock request.
• No maintainer invitation, accepted issue/PR, or corrected release exists yet. Homebrew/homebrew-core#297372 remains open and blocked at v0.7.0.

@badlogic @kevinjosethomas please invite/vouch @kaluli123123 or apply 7acfae7b internally. The stable release acceptance test must verify both the emitted filename and its two top-level runtime exports before @kennethnym updates the preserved Homebrew PR.

[fettpl]

Status delta — 2026-09-02

• v0.9.1 is now the latest stable release. I inspected its official archive (sha256:573bce0cd004fc62052e9a924089941b7f39266ab71e66a94c85a1f9d35835ba): dist/bundle/amazon-bedrock.js is still absent, while the bundle still calls importNodeOnlyProvider("./amazon-bedrock.js") and expects streamBedrock / streamSimpleBedrock. The release workflow passed, but the artifact defect remains.
• Correction to my earlier status: #1379 already tracks emitted provider-bundle closure, explicitly including Bedrock/v0.7.0 & v0.7.1 release tarball is missing dist/bundle/amazon-bedrock.js, breaking the amazon-bedrock provider #751. @kevinjosethomas reopened it on August 15. I missed it in the earlier title-only search; an accepted tracking issue does exist, though no external implementation invitation is recorded in these discussions.
• #1970 now proposes Bun as the primary runtime and compiled binaries as the supported install/update path. It remains unmerged and requires review; its current build/test/artifact-smoke checks pass. This may change the Homebrew packaging approach, so it should be coordinated before revising the formula.
• Homebrew/homebrew-core#297372 remains open and unchanged at v0.7.0. No duplicate submission was created.

@sethkarten @kevinjosethomas please confirm whether #1379 will deliver a corrected Node archive or #1970 is intended to supersede that path. Before @kennethnym updates the existing Homebrew PR, we need a verified stable artifact and a supported source-build path preserving shared Homebrew libzmq linkage and Homebrew-owned updates. I will track those decisions here without reopening closed PRs or submitting an unsolicited replacement.

[fettpl]

Status delta — 2026-09-03

• Bun migration #1970 advanced to 3125a8618 after rebasing onto main at cd10724fe. The author reports fixes for broken activation-symlink repair and explicit-path installation without HOME; both review threads are resolved. The author also reports passing the exact advertised version to the updater to address the earlier metadata propagation race.
• I verified that the current hosted CI passes, including build, package tests, Python runtime, and artifact smoke. Macroscope skipped its latest review because of its configured cost limit; that is not a completed review. build: make Bun the primary runtime #1970 remains unmerged and review-required. I have not independently run its compiled artifacts.
• No new stable release or release-asset replacement is available: v0.9.1 retains the same archive hash inspected yesterday, with the Bedrock defect unresolved. #1379 remains open, and Homebrew/homebrew-core#297372 remains unchanged at v0.7.0.

Next owners remain @sethkarten @kevinjosethomas for the supported packaging decision and corrected release, then @kennethnym for the existing formula. Passing migration CI does not yet establish Homebrew-compatible source builds, shared libzmq linkage, or Homebrew-owned updates; those checks remain required before finalization.

[fettpl]

Status delta — 2026-09-04

• zeromq.js v6.7.0 was published. I inspected the official npm tarball (sha1:0a678617d72f9d0425b61a9238880c30ae36a0d2): its CMake configuration retains ZMQ_SHARED, skips vcpkg in that mode, discovers libzmq through pkg-config, and links PkgConfig::ZeroMQ. The Homebrew shared-libzmq build path therefore remains available in the new release; I did not rerun the full formula preflight today.
• Bun migration #1970 advanced to 7163e9c1 after another main merge. Its current hosted CI passes, but the PR remains unmerged and review-required. Two new threads are unresolved: a CodeQL test warning and a high-severity installer finding that updating an already-installed but inactive version can delete files still used by a resident process.
• Prime Agent v0.9.1 and its assets are unchanged, so the verified Bedrock release defect remains. #1379 is still open without a new maintainer update. Homebrew/homebrew-core#297372 remains open and unchanged at v0.7.0.

@sethkarten should resolve the new #1970 installer finding and review gate; @kevinjosethomas still owns the supported release/packaging decision; @kennethnym should keep the existing formula unchanged until that decision produces a verified stable artifact. No duplicate Homebrew submission was created.