[harsha09]

Summary

Fixes #59. A project can now describe its own team in plain files, which is the base the later role-bot work reads.

• sdd team init --template software writes .sdd/team.yaml and the product-manager, architect, product-owner, dev-lead, and developer roles. solo and research are the other shipped templates. A second run, or a role file that already exists, writes nothing.
• The team file stores bots, a work-in-progress limit per bot and optionally per role, human approvers by name, the rooms commit switch, and a branch pattern that includes {bot}. sdd team show marks a human (you) when the name matches git config user.name.
• sdd role create <name> --template software/developer copies a shipped role. developer alone is ambiguous. A role created with only a label and a job does not grow empty list fields.
• The four host stubs (sdd, sdd-planner, sdd-implementer, sdd-reviewer) state what they own, what they never do, what they check, and when they ask.

sdd new, sdd next, and sdd skip from the CLI on main drove this change. No separate CLI defect showed up. sdd verify reports NOT RUN because the feature workflow has no verify.commands. That is the existing empty-command result.

Test plan

• Full core vitest (281 tests)
• CLI integration tests, including team init and role create from a template (30 tests)
• tsc --noEmit for core and cli
• biome check on packages/core/src and packages/cli/src