CodeVetter · Repo Unpack · Contributor handoff
rollup/rollup
Start with architecture and scoped instructions, then follow the affected phase and environment adapters. Preserve generated-file ownership and conservative tree-shaking contracts. Tests and CI were inspected, not executed, and this bounded brief supplies no passing-test or coverage guarantee. The commands below describe future authorized implementation checks; none were run during this audit.
- Read AGENTS.md and scoped src/rust/test instructions before changes; production code uses descriptive names, localized behavior, and short comments only for non-obvious information.
- Respect LOAD_AND_PARSE → ANALYSE → GENERATE layering; AST nodes access module capabilities through astContext, and user-facing diagnostics use log factories plus URL constants.
- Tree-shaking changes must retain pessimistic defaults, schedule new passes after invalidating inclusion decisions, and invalidate memoized dependent values after reassignment.
- Edit AST schema/generators instead of generated decoders; preserve buffer alignment, word-index references, endianness, UTF-16 positions, and error-node protocols.
- Verify browser capability changes against code: custom fs is supported despite the narrower ARCHITECTURE.md description; default fs methods throw and replacements are explicitly registered.
- For future authorized checks, JavaScript changes use update:js and Rust changes use update:napi; build:quick builds NAPI plus CommonJS and omits browser/ESM artifacts needed by some tests.
- Prefer function regression samples for executable behavior, form for removed code, and chunking-form for multiple outputs; watch tests live in index.js, and new plugin tests should avoid the legacy hooks suite.
- Rebuild artifacts before testing, remove solo selections, and remember fixture runners change cwd; tests and CI here were inspected rather than executed, so configured checks provide no observed pass result.