configure.sh uses 'set -euo pipefail'; fleet AGENTS.md mandates 'set -Eeuo pipefail'

[ptr727]

Fleet AGENTS.md ("All scripts use set -Eeuo pipefail") and every native downstream script follow the -E form, but the canonical repo-config/configure.sh (hub develop) opens with set -euo pipefail - no -E, so ERR traps don't inherit into functions/subshells.

Surfaced by Copilot review on a downstream promotion PR (HomeAutomation-Config #22) flagging the carried copy against the repo convention. Downstream copies are verbatim carries per the carry policy (and #330 treats divergence from the reference as drift), so the fix belongs here; carries pick it up on their next refresh. The trimmed merge-bot reference's inline run: steps have the same pattern if inline snippets are meant to be covered by the rule - if they are not, a one-word scope clarification in AGENTS.md ("script files") would also settle the reviewer noise.

No downstream action taken - the carried copies stay verbatim until the hub updates.

[ptr727]

Fixed in #350 (develop 878e1cc) - though not as filed, worth recording why.

The premise was inverted. The hub's AGENTS.md said set -euo pipefail and configure.sh used exactly that - they already agreed. The -Eeuo mandate this issue cites exists only in HomeAutomation-Config's carried AGENTS.md, which had drifted from the hub. And there are no trap ... ERR anywhere in the fleet, so -E is functionally inert today. Taking the issue at face value would have changed the canonical hub script to match a drifted downstream copy.

Resolution (owner's call): adopt -Eeuo at the hub as the better default and let the carries converge on it. Swept all 26 occurrences (4 hub workflows, configure.sh, 7 catalog workflow snippets, 2 devcontainer post-create.sh). The AGENTS.md rule also resolves the scope ambiguity raised in the last paragraph - it now covers "every bash surface: a multi-line run: block and every committed .sh script alike", so inline snippets are explicitly in scope, and WORKFLOW.md matches.

Copilot then caught that strengthening the rule left one hub snippet non-compliant (build-executable-task.yml's run: block started straight at dotnet publish); fixed, and a re-scan of every *.yml confirms no multi-line bash run: block lacks the line now.

The downstream AGENTS.md divergence that produced this issue is more evidence for #305.