Track bytecode-first bundling and executable packaging

Goal

Deliver a bytecode-first packaging pipeline that starts with reusable .gcbundle artifacts and ends with signed distributable executables.

Scope

• Coordinate Issues #152-#160.
• Keep the work bytecode-first.
• Treat .gcbundle as the intermediate deployable artifact.
• Track native executable packaging and signing as later phases layered on top of .gcbundle.

Child Issues

• #152 Add a module content/provider abstraction for non-filesystem module loading
• #153 Define and implement the .gcbundle multi-module bundle format
• #154 Add a bundle-backed resolver and runtime source registry
• #155 Make bytecode imports load bundled bytecode modules natively in the VM
• #156 Add a separate BundleBuilder executable that packages a module graph to .gcbundle
• #157 Teach ScriptLoader to execute .gcbundle artifacts in bytecode mode
• #158 Add bundled asset support and GocciaScript.bundle runtime API
• #159 Add host-target executable packaging that wraps .gcbundle
• #160 Document and automate signing/notarization flow for packaged outputs

Dependency Order

1. #152
2. #153
3. #154
4. #155
5. #156
6. #157
7. #158
8. #159
9. #160

Release Readiness Definition

• .gcbundle runs in ScriptLoader.
• Native packaging works on at least one host platform.
• Signing/notarization flow is documented.

Notes

• Issues #152-#155 are general-purpose runtime architecture improvements.
• Issues #156-#158 already deliver a shippable artifact model: .gcbundle.
• Only Issues #159-#160 are specific to native executable distribution and signing.

Start by reading child Issues #152-#160 in the listed dependency order, then review the ScriptLoader and BundleBuilder entry points. Track the .gcbundle artifact through bytecode execution, native packaging, and signing; the work is done when ScriptLoader runs bundles, one host platform produces an executable, and signing is documented.