fix(patterns) redraw the final seven ASCII diagrams under 78 columns

[mjmirza]

Batch 14, the final batch, of the ASCII-diagram width
remediation pass.

Seven entries redrawn so every diagram line stays under 78
columns, across families 08, 09, 10, 13, 16, 17, and 24.

• rate-limiting
• semaphore
• serverless-deployment
• signals
• lens
• late-chunking
• replayable-log

Multi-branch and horizontal-timeline layouts (an enforcement
pipeline fanning to admit or deny, a semaphore's wait set, two
parallel execution envs, a naive versus late chunking
comparison, a partition log with three consumer cursors) are
redrawn as vertical chains or compact inline sequences with the
branch or timeline relationship named in prose, the same
simplification used in batches 7 through 13.

This closes out the width-remediation pass. All 134 entries
originally flagged over 78 columns in the frozen Phase 2 audit
are now fixed across 14 PRs (batches 1 through 14).

Gates run clean. check-structure.py (884/884), check-family-names.py,
check-prose.py (925/925), markdownlint-cli2 0.23.2 (0 issues),
validate-refs.py --strict (every citation resolves), check-code.py
--strict (2826 compiled, 0 failed). gen-indexes.py regenerated all
affected family README.md tables.

[mjmirza]

REVIEWED. Approve. This is batch 14, the final batch, of the ASCII-diagram width
remediation pass. Seven diagram sections redrawn under the 78-column
limit, spanning seven families (08, 09, 10, 13, 16, 17, 24).

Real diff confirmed via gh pr diff --name-only. 14 files, 7 content
entries plus 7 family README.md index regenerations, matching the
expected shape.

CI. every real check (structure and prose, code samples compile,
citations resolve, markdown style, claim check, PR security check)
reports pass across both check-suite runs on this PR. The two
skipping entries are the claim check and PR security check on the
pre-merge-fix commit, superseded by the green re-run on the
post-merge-fix commit.

Merge history. this PR conflicted with batch 13 (PR #436) on one
family README, 08-cloud-distributed, since both batches touched that
family in parallel branches. Resolved via the standard recipe. git
fetch, merge origin/main, take main's version on the conflicted
README, regenerate all family indexes fresh via gen-indexes.py,
commit the regeneration separately, push. PR flipped from
CONFLICTING to CLEAN/MERGEABLE and CI re-ran green on the merge-fix
commit.

Gate sequence (check-structure.py 884/884, check-family-names.py,
check-prose.py 925/925, markdownlint-cli2 0.23.2 0 issues,
validate-refs.py --strict all citations resolve, check-code.py
--strict 2826 compiled 0 failed) all ran clean locally before push,
and gen-indexes.py was re-run after the merge-fix so the conflicted
family README byte count reflects both batch 13 and batch 14
correctly.

This closes the entire width-remediation pass. Confirmed via
/tmp/filter_remaining.py against the frozen Phase 2 audit
(diagram_audit_results3.txt, 134 originally flagged entries) that
zero entries remain outside the fixed set, across 14 PRs (batches 1
through 14).

Single review pass, low blast radius. pure diagram-fence replacements
in already-published entries, no prose or reference changes outside
the diagram sections and the generated index tables.