[v0.91.8][csdlc-v2][tooling] Keep all issue lifecycle writes in the bound worktree

[danielbaustin]

Problem\nTyped binding can update the canonical issue record in the primary checkout while the newly created bound worktree lacks the ignored .csdlc issue state. Doctor/finalize then fail against the actual implementation worktree, and the primary checkout accumulates lifecycle artifacts.\n\n## Definition of Done\n- csdlc-bind materializes or verifies the issue record, cards, lock, prepared artifacts, and evidence root in the declared bound worktree.\n- Any write attempted against primary main fails closed unless the operation is explicitly bootstrap/read-only.\n- Bound-worktree doctor, validate, review, publish, and closeout operate on the same repository root as implementation.\n- Add a regression test covering a newly created worktree with ignored .csdlc paths.\n- Preserve #5655 and existing issue records; no manual record copying is required.\n\n## Constraints\n- Rust binaries only; no Python or shell lifecycle wrapper.\n- Keep the primary checkout clean on main.\n- Do not weaken claim, lock, or exact-revision protections.