chore(release-profile): seed advisory.yaml (mode=release advisory tier)

[Jammy2211]

Summary

Seed config/build/advisory.yaml — the workspace half of the PyAutoHeart mode=release advisory tier (PyAutoHeart#74).

Declares the known-slow real-search scripts (real Nautilus fits + finite-difference JAX gradients) that flake around the per-script timeout cap — the 2026-07-13 re-val #3/#4 flip-flop population. With the tier (PyAutoBuild#153 / PyAutoHeart#75), a timeout on a declared script still runs+reports but is advisory (YELLOW), not release-blocking; a timeout on any undeclared script is still RED. Unlike a no_run SLOW-skip, these scripts keep running, so coverage is preserved and the list converges.

Inert until PyAutoBuild#153 merges (the run_python.py advisory loader). Library-first: this waits behind Build#153 + Heart#75.

Test Plan

• Every advisory pattern .py-anchored and verified to match exactly one real script.
• After PyAutoBuild#153 merges: a mode=release run records these as timeout_advisory (not timeout) if they exceed the cap.

Generated by the PyAutoLabs agent workflow.

[Jammy2211]

Closing in favour of the simpler no_run approach.

On reflection the advisory tier is more machinery than warranted here. Its core premise — that no_run SLOW-skips erode coverage forever and never converge — is substantially handled by the maintainer's periodic hygiene sweep of no_run. And for scripts that reliably exceed the cap, a skip and an advisory-timeout are equivalent anyway (a timed-out script asserts nothing that run).

Instead, the affected slow real-search scripts will be added to each workspace's no_run.yaml as SLOW and reviewed via hygiene over time — no new mechanism, no second config convention, smaller footprint. See PyAutoHeart#74.