fix(types): publish declarations under trackable names - #928
Draft
0xpatrickbot wants to merge 9 commits into
Draft
fix(types): publish declarations under trackable names#9280xpatrickbot wants to merge 9 commits into
0xpatrickbot wants to merge 9 commits into
Conversation
Expose the package root through a publication-safe declaration barrel so npm packing retains the declared type entry point.
Move the package contracts into checked TypeScript while keeping the existing type entry surface available through a publication-safe barrel.
Move the public gateway contracts into checked TypeScript source and expose them through a thin declaration entry barrel.
Keep the eval and package declaration barrels publication-safe while moving the authored contracts through checked TypeScript project inputs.
Convert the hand-authored declaration source into checked TypeScript with a thin publication barrel so type generation sees every exports target.
Move the package declaration twins onto the publication-safe naming convention, follow exo-stream source types in the extractor, and constrain declaration emit to the checked inputs.
Rename the remaining bot-only declaration barrels onto the publication-safe convention and align package metadata and TypeScript project inputs with those entry points.
Reject tracked declaration files that are neither publication-safe by convention nor explicitly exempted at the repository root.
Enable publication for the capability packages whose declaration entry points were refreshed, with explicit public npm access where required.
0xpatrickbot
force-pushed
the
fix/declaration-file-naming
branch
from
August 6, 2026 01:42
f1e9820 to
626c361
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs: #884
Description
Rename hand-authored declaration entry points to publication-safe
*.types.d.tsfiles, move substantive declaration bodies into checked.tssources with thin publication barrels, and update package type metadata, exports, and build inputs accordingly. Add repository-wide declaration naming checks so tracked declarations follow the convention or have an explicit root ignore exception. The affected capability packages are publishable with public access, and the agent-tools extractor follows exo-stream's checked type source so generated declarations retain concrete passable-reader contracts.Security Considerations
This changes declaration packaging and package visibility, not runtime authority or confinement boundaries. No new capabilities or remote calls are introduced.
Scaling Considerations
The uniformity check adds one repository-wide tracked-file scan. Runtime CPU, memory, storage, and message behavior are unchanged.
Documentation Considerations
Consumer import paths remain stable through package exports. Downstream maintainers only need to know that published tarballs now include the declared TypeScript entry points and that newly authored declaration barrels should use the
*.types.d.tsnaming convention.Testing Considerations
Affected package lint and runtime suites, composite declaration builds, type-contract tests, package-uniformity tests, the live npm packlist audit, all-package tarball construction, API docs, formatting, pre-dispatch gates, and shell checks pass. Root lint's formatting stage passes, while its ESLint stage retains pre-existing project-service failures in unchanged
packages/familiar,packages/lal, andpackages/module-sourcefiles.Compatibility Considerations
Existing JavaScript and TypeScript import specifiers are unchanged. Declaration entry files move behind updated metadata, and previously private capability packages become publicly packable.
Upgrade Considerations
No live state migration is required. Publishing the refreshed packages replaces tarballs whose declaration metadata previously pointed at files omitted by npm packing.