| 1 | # Publishing A Package |
| 2 | |
| 3 | Compare the package manifest with a neighboring published package in the same |
| 4 | family. |
| 5 | |
| 6 | - Keep development `exports` and `publishConfig.exports` aligned by key. |
| 7 | Source targets become their intended built targets; blocked internal and |
| 8 | legacy paths remain blocked. |
| 9 | - Check current AI documentation copy tooling and the package `files` list for |
| 10 | every file required in the published payload. |
| 11 | - Ensure each public source entrypoint has exactly one published counterpart |
| 12 | and no internal entrypoint becomes exposed. |
| 13 | |
| 14 | Run the current root build so publication payload generation executes. Create a |
| 15 | tarball in a temporary destination without publishing, inspect its file list, |
| 16 | and inspect the packed `package.json` whenever manifest transformation matters. |
| 17 | |
| 18 | This branch is complete when package and root checks pass and the packed |
| 19 | surface contains exactly the intended files, exports, and metadata. |