| name | quality-remediation |
|---|---|
| description | Use when workspace reliability defects appear as missing root packageManager metadata, dead dependency peer warnings, fake lint coverage, or CI commands that bypass the root workspace contract. |
Fix reliability defects at the contract boundary instead of suppressing symptoms.
- Root workspace commands fail because package-manager metadata is missing.
- Install logs show peer warnings for libraries with no active imports.
- A package exposes a
linttarget but the workspace contract does not execute a real static check. - CI runs package-local commands that hide a broken root workspace path.
- Warning, lint, or security findings need removal by root cause.
- Reproduce the failure or warning from the repo root.
- Trace the contract boundary causing it: root manifest, package manifest, compiler config, or workflow.
- Confirm active imports before removing any dependency chain.
- Remove dead config with the dead dependency, such as JSX settings after
.tsxsources disappear. - Make package lint commands execute a real static check.
- Update CI to use the root workspace contract and derive tool versions from canonical metadata.
- Re-run install, lint, test, and build, then keep smoke paths that prove packaged artifacts still work.
bun run buildfails with missingpackageManager-> add rootpackageManagerusing the installed Bun version.bun installwarns about Ink or React peers without imports -> remove the unused dependency chain and refresh the lockfile.bun run lintis hollow -> add a packagelintscript that typechecks or lints real sources.- Workflow runs
cd packages/... && bun run buildwhile root build is broken -> switch CI back to rootbun runcommands and keep smoke steps after build.
- Pinning CI to
latestinstead of the rootpackageManagercontract. - Keeping dead dependencies because they were once planned for future features.
- Leaving stale TS JSX config after the last
.tsxfile is gone. - Treating warnings as acceptable background noise.