garrytan 30d2904c66 0.3: published lines cannot break a fixed fence ...

evals.yml wraps collector-outcomes failures in a fixed three-backtick fence
for the PR comment, so those lines (and eval:pass-rates output meant for the
tracking issue) go through sanitizeFixedFenceLine: cleaned like every
published line, with backticks turned into quotes. Inline published text
also neutralizes backticks.

2026-10-04 18:02:05 +00:00

..

eval-history.ts

0.3: published lines cannot break a fixed fence

2026-10-04 18:02:05 +00:00

free-home-guard.ts

v1.91.16.0 fix: safe installs and upgrades, skills start everywhere, truthful completion (parallel wave) (#3014)

2026-10-03 07:54:09 -07:00

paid-cases.ts

v1.91.19.0 fix: severe fix wave (truthful gates, no lost memory, every host finds gstack) (#3025)

2026-10-04 07:58:41 -07:00

paid-plan.ts

v1.91.19.0 fix: severe fix wave (truthful gates, no lost memory, every host finds gstack) (#3025)

2026-10-04 07:58:41 -07:00

paid-report.ts

0.3: published lines cannot break a fixed fence

2026-10-04 18:02:05 +00:00

published-text.ts

0.3: published lines cannot break a fixed fence

2026-10-04 18:02:05 +00:00

shard-engine.ts

v1.91.16.0 fix: safe installs and upgrades, skills start everywhere, truthful completion (parallel wave) (#3014)

2026-10-03 07:54:09 -07:00