wushenghua 8e1c4a80a1 docs(deploy): the keychain failure is session-scoped, not an ACL allow-list ...

Measured on this machine: from a Background session (a plain `ssh localhost` is
enough) `security show-keychain-info` already fails with "User interaction is
not allowed" (exit 36) and codesign returns errSecInternalComponent, while the
same command in Aqua reports the keychain unlocked and codesign succeeds. So the
key's ACL is not what blocks us - the session cannot reach the keychain at all -
and granting the key "allow all applications" would not help.

Correct the guidance in sign-build.sh and docs/local-deployment.md (both added
earlier today) accordingly: run the deploy from a Terminal window, or unlock the
keychain inside the Background session with the password
(`security unlock-keychain -p`, the CI-style recipe; the interactive form cannot
prompt there). Verified the failure path still prints the new text.

2026-09-18 01:55:29 +08:00

..

dev

feat(media): add audio and file display (#1405)

2026-08-08 13:46:59 +08:00

tooling

feat(media): add audio and file display (#1405)

2026-08-08 13:46:59 +08:00

deploy-local.sh

fix(deploy): retry the hub health check for up to 20s

2026-09-17 09:45:21 +08:00

deploy-remote.sh

feat(deploy): install to the fixed path again (one TCC grant, verified rollback)

2026-09-17 09:38:08 +08:00

prune-backups.sh

feat(deploy): install to the fixed path again (one TCC grant, verified rollback)

2026-09-17 09:38:08 +08:00

sign-build.sh

docs(deploy): the keychain failure is session-scoped, not an ACL allow-list

2026-09-18 01:55:29 +08:00