Jeffrey (Dongkyu) Kim b1a7d79136 Keep the documented sops bootstrap path executable as written ... The first end-to-end verification exposed a mismatch between the documented .sops.yaml regex and the temporary plaintext filename used during bootstrap. The rule now matches both secrets.env and secrets.env.plain so the setup skill works exactly as documented. Constraint: Setup docs must be mechanically correct, not just conceptually correct Rejected: Change the bootstrap filename instead | broader docs churn for no practical gain Confidence: high Scope-risk: narrow Reversibility: clean Directive: Re-run the documented setup path after any future secret-handling doc edits Tested: bash scripts/validate-skills.sh Tested: sops --encrypt via .sops.yaml + sops exec-env with dummy secrets Not-tested: Windows-specific setup commands beyond documentation review		2026-03-25 01:00:03 +09:00
..
.sops.yaml.example	Keep the documented sops bootstrap path executable as written	2026-03-25 01:00:03 +09:00
secrets.env.example	Remove the account requirement from k-skill secret handling	2026-03-25 00:55:26 +09:00