chore: untrack mkcert local TLS files from version control

Both deploy/local-tls/localhost.crt and localhost.key were accidentally force-tracked. Since we use mkcert each developer generates their own pair — committing either file is meaningless (the cert is signed by the local mkcert CA, which is machine-specific).

- Remove [force_track] block from .museignore; add both files to ignore patterns - Untrack both files (rm --cached; files remain on disk) - Fix ssl.md: correct the incorrect claim that localhost.crt is committed

sha256:3caced6de13d175d2041ae1c6a53e753dda8ca6b2cc52b8193b6a18ebbe46af6 sha

sha256:3aafd5d4ac38b8efcb6030fdefe87cd45d11922569e297d952358906be4d7700 parent

sha256:b0f7d4ec6bc40e2e9a89a61cf83331fe6a2bba5b8560dc941a3e542302ed6d3b snapshot

← Older Oldest on task/remove-committed-tls-certs

All commits

Newer → Latest on task/remove-committed-tls-certs

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:3caced6de13d175d2041ae1c6a53e753dda8ca6b2cc52b8193b6a18ebbe46af6 --body "your comment"

Provenance signed

AI Agent

claude-sonnet-4-6

Bump BREAKING

Agent claude-code

Breaking

deploy/local-tlsdeploy/local-tls/localhost.crtdeploy/local-tls/localhost.key

Signature Cryptographically verified

Snapshot

ID sha256:b0f7d4ec6bc40e2e9a89a61cf83331fe6a2bba5b8560dc941a3e542302ed6d3b

Files 0

Browse tree at this commit →

Commit

SHA sha256:3caced6de13d175d2041ae1c6a53e753dda8ca6b2cc52b8193b6a18ebbe46af6

Parent

sha256:3aafd5d4ac38b8efcb6030fdefe87cd45d11922569e297d952358906be4d7700

Branch task/remove-committed-tls-certs