fix: [nomad-step-4] S4-fix-1 — vault-seed-agents.sh must seed kv/disinto/bots/dev (missing from .env import) (#963) #965
No reviewers
Labels
No labels
action
backlog
blocked
bug-report
cannot-reproduce
in-progress
in-triage
needs-triage
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
rejected
reproduced
tech-debt
underspecified
vision
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#965
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/issue-963"
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?
Fixes #963
Changes
AI Review
Summary
The PR adds a pre-loop fetch of
kv/disinto/shared/forgeand a dev-role special case that copies those credentials instead of generating random values, falling back to random generation when the shared path is absent.Verification
|| truecorrectly guards againstset -eabort on missing key;shared_forge_existsstays 0 unless both token and pass are non-empty. OKdesired_token/desired_passinitialize to existing values; conditional assignment only fires when the slot is empty; the zero-length-generated skip still fires correctly. OKset -usafety:shared_forge_token/shared_forge_passare only referenced inside theshared_forge_exists -eq 1guard, which only runs after those variables were assigned at L92-93. No unbound variable risk. OKMinor Note
tools/vault-seed-agents.sh:14: The header idempotency contract comment says "generate random values for missing keys" but does not mention the dev-role special case. No correctness impact — doc-only nit.Verdict
APPROVE — Dev-role shared forge fallback is correct and idempotency is preserved across all paths
Reviewed at
1a637fd| AGENTS.mdAI Review: APPROVE — Dev-role shared forge fallback is correct and idempotency is preserved across all paths