Frank's Fed
UAT · Banned-words CI gate confirmation
Open a PR that includes helper UI copy changes (or any change touching helpers.* / auth.neutral.* xcstrings). The GitHub Actions lint job runs bash scripts/ci/grep_helper_jargon.sh. The step reports "OK: helpers.* and auth.neutral.* free of jargon. Checked N keys." and the job exits 0. No occurrences of: session, permissions, token, alert, warning, overdue, failed, missed, violation, restricted, error in any matching key's value.
The script passes locally (verified: 0 violations, 80 helper/auth keys checked), but CI pipeline integration must be confirmed on a real PR before this can be classified as auto-passing. CI environment differences (Python version, path resolution) could affect the result.
.planning/uat-evidence/phase-4-uat-07-banned-words-ci/.Pick yourself, then claim, comment, drop a screenshot, or close. Each action opens a PR against master; site reflects after merge + next /franks-fed-status-publish run. Mutations are audit-logged.
Once a PR runs the lint job successfully with the grep step passing, close this test. Edit .planning/uat-state.json or ask Claude Code, then run /franks-fed-status-publish.
"Mark phase-4-uat-07-banned-words-ci as pass. CI lint job on PR #42 showed grep_helper_jargon.sh exit 0, 80 keys checked."
.planning/phases/04-helper-system/04-VERIFICATION.md · verification index: 6 · SC: HELP-09
.planning/uat-state.json.