sdd-init — calibrate the repo before the SDD chain

Step zero for technical SDD work: read the repo, detect how it should be built and tested, refresh the cheap skill registry, and write one durable config:

02-DOCS/wiki/sdd/config.yaml

That config is the runtime contract later phases read before choosing commands, TDD strictness, artifact paths, review budget or skill briefs. sdd dispatches the phases that consume it, init owns first contact and user profiling, harness owns 01-TOOLS/ and 02-DOCS/ scaffolding. This skill only calibrates.

Inputs

Read-only first:

• package.json, lockfiles, pnpm-workspace.yaml, pyproject.toml, requirements.txt, go.mod, pubspec.yaml, Dockerfile, .github/.
• Existing 02-DOCS/wiki/sdd/config.yaml, if present.
• 02-DOCS/wiki/harness/user-profile.md, if present, for accompaniment level only.
• .rsc/skill-registry.json, if present, to decide whether it is stale or missing.