fix(export): continue after invalid identifier to avoid stale env sync

[chaliy]

Motivation

• Interpreter post-processing always syncs export operands into env, but the export builtin previously returned immediately on invalid identifiers causing later valid NAME=VALUE operands to be skipped and stale values to be exported.
• Align export behavior with Bash semantics and preserve readonly handling by making per-operand failures non-fatal to further argument processing.

Description

• Change crates/bashkit/src/builtins/export.rs to stop returning early on invalid identifiers and instead append an error to stderr, set exit_code = 1, and continue processing remaining args.
• Preserve existing readonly-error reporting and behavior (still sets exit_code = 1 and continues).
• Add a regression test export_continues_after_invalid_identifier_and_exports_good_args in crates/bashkit/tests/blackbox_security_tests.rs that exercises GOOD=old; export 1BAD=x GOOD=new and asserts the command exits nonzero while GOOD is updated and exported.

Testing

• Ran the targeted test with cargo test -p bashkit --test blackbox_security_tests finding_readonly_bypass::export_continues_after_invalid_identifier_and_exports_good_args and it passed (ok).

---

Codex Task

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	bashkit	981276b	Commit Preview URL	May 08 2026, 09:20 PM