[janniklasrose]

Follow-up to the review thread on #6957 (#6957 (comment)).

Problem

The acceptance-test title helper printed \n=== <label> with no trailing newline, relying on a following trace (which prepends \n) to terminate the header line. This had two consequences:

• When a title was followed by non-trace output, the header got mashed onto the output, e.g. === Recorded create-branch request bodies{.
• Authors compensated inconsistently — a bare echo after the title (139 occurrences) or a literal \n appended to the label (~359 occurrences).

Change

title now prints its own trailing newline, so it is self-contained and the mashing is fixed. To keep the common title+trace output tight (no blank line between the === header and the >>> command), trace drops its leading newline when it immediately follows a title; a trace after any intervening output still gets its usual blank-line separator.

The "immediately follows a title" state is tracked by an _after_title flag: title sets it, trace reads and clears it, and a DEBUG trap clears it before any other top-level command. The trap requires set -T because the harness runs the main script in a subshell (readMergedScriptContents in acceptance_test.go), and a FUNCNAME guard keeps it from firing inside the helper functions themselves.

The now-redundant workarounds are removed and all acceptance goldens regenerated.

Net effect on output.txt

• Idiomatic title+trace blocks: unchanged.
• title followed by non-trace output: no longer mashed onto the header line.
• Consecutive section headers: now separated by a blank line.
• Workaround-driven inconsistencies (manual \n, bare echo): removed, so these blocks match the tight majority.

Testing

./task test regenerated via -update; full suite re-run without -update passes. The only failures observed locally are pre-existing/environmental and unrelated to this change: bundle/deploy/mlops-stacks (needs network to clone the upstream template; its output.txt is unchanged here) and bundle/apps/job_permissions (documented-flaky deploy-order output in out.after_first_deploy.txt, which this change does not touch).

This pull request and its description were written by Isaac.