Move weekly profiling operations to lean-pool-automation

[Vilin97]

Move weekly profiling operations into the private automation repository, alongside the other Azure runners. Remove the weekly runner, systemd units, operational guide, and regression tests from LeanPool; retain only the public source-profile link and weekly refresh description in the README.

The complete implementation, automatic dependency recovery, non-notifying health check, tests, and installer now live in lean-pool-automation PR #6. Profiler-specific build and heartbeat fixes remain in lean-source-profiler PR #2.

Validation: all 126 automation tests pass, including the 39 moved profiling tests. Ruff checks/formatting pass for the moved code; the installer passes bash -n. No references to the removed profiling script paths remain in LeanPool. Runtime paths and the existing Azure recording are preserved; notifications remain disabled.

[Vilin97]

Source review at exact draft head 40bf4a9af93e70e3666a9b740ef04b2c1d44c4c9 is favorable for the current public cleanup.

This head changes the proposal's scope: the public runner, regression suite, operational guide and systemd units are retired. Against its original main base 13797a3, the final diff has seven paths, two additions and 1,058 deletions. The transient recovery/health/ref-selection additions are absent. My earlier feature review remains historical and does not certify the private replacement.

The public profile link and recording badge remain; the README's obsolete local operations link is replaced with the weekly refresh description. The removed test suite and runner form the same retired dependency chain. A bounded audit of all 19 retained workflows and the named Makefile, Python package/configuration, README and CODE_QUALITY entrypoints found no remaining retired-path, service-name or environment-variable references in that corpus. No Lean proof source, dependency pin, protected workflow or mathematical quality-rule change is in the final diff.

The private automation migration, external profiler fixes, 126-test result and preserved Azure recording/runtime are owner claims. I did not inspect or operate those replacements, move recordings, install units or rerun profiling. Current public-head CI is PENDING; earlier heads' checks are not transferred.

The draft and operational handoff remain with the owner. Keep the historical recordings and evidence distinct while completing that handoff and current-head checks. The independent infrastructure priority hold remains while exact current main 0c1132c7 has pending CI. All eight required check names are attached there; documentation publication now runs daily or by manual dispatch, with separate PR/merge-group preflight. The earlier Python-only finding belongs to the previous main commit. No queue admission or merge action is taken.