Print package versions without depending on the current directory
The release coordinator runs the command from packages/ui and gets an empty package list. Add an inspect command that finds the workspace root and reports each releasable package.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- CLI design · Filesystem paths · Input validation
Estimated field mix
- Developer tooling100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A team maintains six related packages. Release notes, version changes, and tags are copied between a spreadsheet and a terminal; a failed upload recently left two packages ahead of their dependents. The exercise uses temporary repositories and a fake registry.
Setup prerequisites
- Create a temporary Git repository with three related fixture packages.
- Use a local registry double; no publishing credentials are required.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Running from the root or a nested package produces the same sorted names and versions.
- Private packages are labeled and excluded from the releasable count.
- A directory outside a workspace returns a nonzero exit code and an actionable error.
Implementation constraints
- Read manifests as data; do not run package scripts.
- Stop root discovery at the filesystem root.
Verification to include
- Run inspect from root, a nested directory, and a path containing spaces.
- Pass malformed package JSON and verify that the filename appears without dumping file contents.
Deliverables
- Inspect subcommand and a three-package fixture
Rollout and recovery
Ship as a read-only command first; revert the command registration if root detection regresses.
Value of the work
For the engineer: Practice CLI contracts, graph reasoning, filesystem safety, and recovery from partial work.
For the team: Review how an engineer makes release changes inspectable and recoverable before they affect consumers.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.