CodeVetter · Repo Unpack · Contributor handoff
storybookjs/storybook
Use this report as a source map for the pinned commit, then recheck checkout-specific instructions and implementation before editing. Tests and CI were inspected, not executed; verification commands below are guidance for subsequently authorized implementation work. Investigation covered more than twelve implementation files and three concrete flows, but remains bounded rather than exhaustive. Keep edits within the owning package and preserve contracts across server, manager, preview, and agent transports.
- AGENTS.md is canonical and CLAUDE.md is a reference; start core/preset/service/tools work with the architecture guide and read the linked testing/sandbox/task guides when relevant.
- The contributor environment pins Node 22.22.3 and Yarn 4.18.0 with node-modules linking; prefer existing NX compile/check targets and non-production configurations during routine iteration.
- For later authorized validation, use focused yarn test patterns for utilities and stories with play functions for React behavior; tools attachment E2E requires the running internal UI from the same checkout.
- After authorized edits, repository guidance requires oxfmt formatting from code/, targeted oxlint checks, explicit relative module extensions, and Storybook server/client loggers.
- Before changing agent operations, read the open-service and tools contracts; keep services/toolsets under the same gate, and preserve the distinction between thrown execution failures and returned ok:false outcomes.
- Avoid broad assumptions about CSF mutation: the preferred shared API exposes changed/mutationDiagnostics, while the Controls save implementation explicitly rejects arrow/call CSF2 forms except recognized CSF4 story calls.
- Do not default to yarn start or untemplated yarn task dev; generated sandboxes belong beside the checkout, and accidental generated manager export changes should be excluded from unrelated diffs.
- PRs target next and require Area: Summary plus Manual testing metadata; Danger evaluates trusted base-branch code, and the manually triggered NX workflow should not be mistaken for evidence of automated checks passing.