v0.3.7

fix(claude): admit completed config migration evidence (#312)

## Summary

- match core migration-required semantics when quarantine encounters
retained config-local or global rollback sources
- bind bounded, hash-only object/content evidence for effective legacy
sources and all canonical destinations, then revalidate it immediately
before park
- preserve legacy and canonical config bytes while keeping pending,
unsafe, unavailable, oversized, symlinked, or drifted evidence
fail-closed
- document completed retained migration evidence versus genuinely
pending migration

## Validation

- `go test ./skills/amux-claude/experimental/claude-delegation -run
'TestProviderOwnedInvalidStoreQuarantine|TestQuarantineRetainedCompletedMigrationEvidence'
-count=1`
- `GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=commit.gpgsign
GIT_CONFIG_VALUE_0=false go test
./skills/amux-claude/experimental/claude-delegation -count=1`
- `go test ./scripts -count=1`
- `GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=commit.gpgsign
GIT_CONFIG_VALUE_0=false go test ./... -count=1`
- `go vet ./...`
- `go build ./cmd/amux`
- `python3 -m py_compile
skills/amux-claude/experimental/claude-delegation/claude_delegation.py`
- `gofmt` on the changed Go test
- `git diff --check`

No live Claude/provider call was performed.

Closes #288