Fixed

• Skip npm install for sub-workspaces already covered by root install (only run if workspace has its own package-lock.json).
• publish:local script now unpublishes first for idempotent republish to Verdaccio.

Added

• --packages flag: JSON override to merge/replace packages from config at CLI level
• --only flag: filter which packages to process (renamed from previous --packages filter behavior)
• Improved recursive install output: tree structure with workspace coverage display

Changed

• Install pipeline refactored for better integration with consumer CLIs
• Output shows per-level install status with workspace coverage indicators

Fixed

• Early return in install command skipped npm link phase when all packages in the config had the link attribute. Projects with only linked packages (no store/npm resolution needed) would silently skip the linking step.

Added

• Selective package install: dev-link install [packages...] accepts positional arguments to install only specific packages from the config
  • Packages must be pre-defined in devlink.config.mjs — error if not found
  • Filter applies only to resolution/staging phase; removal of orphan packages and npm install run normally
  • Works with all package types: normal, synthetic, link, dev

Changed

• loadConfig() API: mode and modeConfig can now be undefined when no mode is specified
• Install flow: staging + npm install is now the only flow — npm always runs, no conditional
• MultiLevelInstallOptions: replaced runNpm/runScripts with npmIgnoreScripts

Removed

• --dev and --prod CLI flags: use --mode dev or --mode prod instead
• --npm CLI flag: npm install now always runs as part of the install flow
• --run-scripts CLI flag: replaced by --npm-ignore-scripts
• Legacy "direct copy to node_modules" flow: all installs now go through staging + file: protocol injection + npm install
• Implicit mode detection from process.argv in loadConfig() API

Fixed

• tree command now detects sub-packages under packages/ directories even when no workspaces field is defined — these are marked as isolated children

Changed

• Updated documentation (install.md, configuration.md, AGENTS.md, README) for link attribute

Added

• link attribute for packages in devlink.config.mjs: packages with link skip store/npm resolution entirely and are resolved via npm link after install
• runNpmLink() helper: runs npm link <path> for a local package, resolving relative paths against the project root
• Link support in all three install flows: no-mode, mode+npm (staging), and direct copy
• linked field in InstallResult to track successfully linked packages
• Post-install summary showing linked packages count and paths

Fixed

• Staging directory (.devlink/) is now fully cleaned at the start of every installPackages() run, preventing stale packages from previous executions from remaining between DevLink runs

Added

• dev: true package flag: packages marked with dev: true in the config are injected into devDependencies instead of dependencies in package.json
• The flag is global (independent of mode or manager type) and has no effect on synthetic packages

Added

• Unit tests for exit code propagation in multilevel installer: skipped packages, npm failures, combined failures, fail-fast behavior, and success cases