Repository change workflow

Scope and issue

Start from current origin/main on a fresh task branch without discarding user work. Search open issues before creating one. Claim tracked work once with Working on this in <branch>; close fixed issues through the PR body.

Choose the PR boundary by cohesion:

• combine work sharing a root cause, API migration, files, acceptance criteria, and verification story
• split work that is independently releasable, reviewable, revertible, or likely to conflict
• a PR may close multiple issues with Closes #N
• issue count never determines PR count

Change

Implement the underlying seam and update the owning skill/reference plus generated artifacts. Preserve unrelated work. Public API changes require JSDoc and regenerated API/capability/export artifacts as applicable. Do not create freestanding design documents.

Verify