Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

tools/egg-bundler/docs/output-structure.md (1)

45-47: ⚡ Quick win

Document fallback behavior when bundle-manifest.json is missing/invalid.

This section currently reads as a hard requirement, but runtime code falls back to defaults (baseDir = __outputDir, framework = compiled default) when manifest read/parse fails or fields are absent. Please add one sentence clarifying fallback + likely consequence (app may start with wrong baseDir mappings). Cross-file evidence: tools/egg-bundler/src/lib/EntryGenerator.ts Line 227-246 and Line 282-288.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@tools/egg-bundler/docs/output-structure.md` around lines 45 - 47, Update the
docs to note that reading/parsing bundle-manifest.json is not fatal: when
Bundler/worker fails to read or parse the manifest or misses fields, the runtime
falls back to defaults (baseDir is set to __outputDir and framework is set to
the compiled default) — add one sentence stating this fallback behavior and the
likely consequence that the app may start with incorrect baseDir mappings or an
unexpected framework value; reference the relevant symbols bundle-manifest.json,
baseDir, framework, __outputDir and EntryGenerator.ts to locate the code path.

tools/egg-bundler/docs/output-structure.md:56

• The bundle-manifest.json example shows an absolute baseDir (e.g. /abs/path/to/app), but the worker now uses this value to compute __appBaseDir and pass it into startEgg. If the bundle is meant to be relocatable/self-contained under <outputDir>/, the docs should clarify whether baseDir is expected to be relative to <outputDir> (recommended) vs an absolute build-time path (in which case relocations require rewriting the manifest or keeping the original path layout).

A runtime metadata file produced by `Bundler`. The worker reads `baseDir` and
`framework` from this file during startup, so deployment must keep it next to
`worker.js`. The remaining fields are reference / debug metadata. Shape:

```json
{
  "version": 1,
  "generatedAt": "2026-04-11T00:00:00.000Z",
  "mode": "production",
  "baseDir": "/abs/path/to/app",
  "framework": "egg",
  "entries": [{ "name": "worker", "source": "/abs/path/to/app/.egg-bundle/entries/worker.entry.ts" }],

tools/egg-bundler/src/lib/EntryGenerator.ts (1)

215-216: 💤 Low value

Minor: Inconsistent quote style in generated imports.

Line 215 uses single quotes while line 216 uses double quotes. This is cosmetic but could be unified for consistency.

 import { ManifestStore } from '@eggjs/core';
-import { startEgg } from "egg";
+import { startEgg } from 'egg';

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@tools/egg-bundler/src/lib/EntryGenerator.ts` around lines 215 - 216, The two
import statements use inconsistent quote styles; update the import for startEgg
to match the project's single-quote style used by ManifestStore (i.e., change
the double quotes around "egg" to single quotes) so both imports use single
quotes; look for the import lines referencing ManifestStore and startEgg in
EntryGenerator (symbols: ManifestStore, startEgg) and make the quote style
consistent across them.

tools/egg-bundler/test/EntryGenerator.test.ts:290

• This test passes framework into new EntryGenerator(...), but EntryGenerator no longer uses that option; the assertions only check that the worker reads __framework from bundle-manifest.json at runtime. Keeping the unused option in the unit test setup is misleading. Prefer removing framework here (and validating bundle-manifest.json.framework via Bundler/integration tests instead).

  it('reads a custom framework specifier from bundle-manifest.json at runtime', async () => {
    const gen = new EntryGenerator({
      baseDir: tmpDir,
      framework: '@my-org/framework',
      manifestLoader: createFakeLoader(makeManifest()),
    });