continuous-integration/drone/push Build is passing
abra's pinned-version 'app new' regenerates the app .env from generation hints and drops SECRET_COLLABORA_P_VERSION (the .env.sample ships the line manually — not a generatable secret). Every secret-touching abra command for the app then FATAs 'missing version for secret? (collabora_p)' and the cold base deploy goes RED at install (first seen in the 2026-10-25 weekly sweep's cold tests of the new releases: lasuite-drive never got past install_steps' oidc_rpcs insert). Re-asserting the shipped version pin via EXTRA_ENV restores the sample's contract. Verified live on cc-ci: abra app check passes for the pinned sample env collabora_p only with the line present; repro via 'abra app new -S' on 0.12.0+v0.21.0 dropped the line deterministically.