Make the runbook's commands paste-safe

[ptr727]

Fixes the two placeholder findings Copilot raised on the promotion #517, plus the six more of the same class.

This has to land on develop first: #517's head isdevelop, and develop carries a pull_request rule, so the promotion cannot be fixed in place.

The defect

OPERATIONS.md wrote shell placeholders as <owner>/<repo>. A POSIX shell parses < as input redirection, so pasting one is a syntax error, in a file whose entire purpose is being pasted:

$ repo-config/configure.sh check <owner>/<repo>
bash: syntax error near unexpected token `newline'

The bracket form pastes cleanly, and STANDUP.md already writes the same command that way:

repo-config/configure.sh check [owner/repo] [release|operational]

So the runbook was both unpastable and the odd one out against the repo's own convention.

Scope: eight, not two

Copilot reported two, one inline and one suppressed. Looking for the whole class found eight across six shell blocks: the prose_lint.py invocation, both configure.sh lines, the branch-recovery git push, both gh run examples, the gh api base-retarget, and two spec/audit.py calls.

Verified by parsing, not by eye

Every sh block was run through bash -n:

6 sh blocks, 0 with syntax errors

That check earned its place. A first pass grepping <[a-z|-]*> reported zero remaining and the parse test still failed block 3, because <RepoName> is uppercase and the pattern was lowercase-only. Checking the property directly caught what checking a proxy for it missed.

Verification

bash -n over every sh block 6 blocks, 0 errors
grep -cE '<[A-Za-z|_-]+>' OPERATIONS.md 0
editorconfig-checker (docker, canonical) clean
markdownlint-cli2 (docker, canonical) 0 issues
prose_lint OPERATIONS.md (charset, dupword, spelling, charset-unknown, dash, semicolon, sentence-split) clean

Once this merges, #517 picks it up automatically, since its head is develop.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Updates OPERATIONS.md runbook examples to use paste-safe placeholder syntax (square brackets) instead of HTML-escaped angle brackets, so copied commands no longer trigger shell redirection parsing errors. This aligns the operations runbook with the repository’s existing placeholder convention and supports the develop-first promotion workflow described in the PR metadata.

Changes:

• Replaced <...> / <...> placeholders with [...] across runbook command examples (prose lint, audit, configure, branch recovery, gh run, and gh api).
• Ensured all updated shell snippets remain syntactically valid when pasted.