feat(shell): give ssm-get a callable form on PATH #1314
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agentic-os!1314
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/pp94"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #1308. Kai chose the callable form over interactive-only.
What changed
ssm-getwas a shell function inshell/common.sh, so scripts, non-interactive shells, and agent tool calls could not reach it. Each one restated the rawaws ssm get-parameter --with-decryptioncall instead, which is the duplication the single-owning-source convention exists to prevent. It had been written down twice, most recently while working #1137.scripts/ssm-getholds the logic, with the same<name> [profile] [region]shape and the same defaults.PATHthrough the same~/.local/binlink as the other wrappers, carried byapply-shell-links.just apply-shell-linkskeeps the helper working with no gap.README.md,docs/install.md, and thetooling-zshskill say which surface is the implementation and which is the delegator.Verification
uv run pytest tests/- 730 passeduv run pre-commit run --all-files- cleanbash -nandzsh -nonshell/common.sh, then a live fetch of/forgejo/coilyco-ops/api-tokenthrough the functionAlso settled, outside this diff
#1307 is answered:
commit.gpgsignis true on workstations, bot seats left unsigned. It is nowtrueon kais-macbook-pro, and the commit in this PR verifies%G?=G, so the signing path added by #1306 is live rather than merely available. The fleet rollout for the other workstations belongs to the ansible shell role in infrastructure, per the authoring-versus-rollout contract, and is tracked on #1307.