[codex] Cover NOC low-disk handoffs in Knowledge

[Svaag]

Summary

• add reviewed OKF context for the noc BGP snapshot root filesystem incident
• seed retrieval for NOC low-root-filesystem/BGP snapshot handoff tasks so the context pack includes the specific postmortem instead of only generic host refs
• add retrieval and Engineering Loop context-pack evals, then refresh exports, eval reports, and quality reports

Dependency

• Source ref points at AS215932/network-operations commit e0e643a1f5e1fefdb458478e468fbf6b3bca13b2 from network-operations PR #336.

Validation

• uv run ruff check src tests
• uv run pytest
• uv run hyrule-knowledge validate okf
• uv run hyrule-knowledge export --check
• uv run hyrule-knowledge eval --check
• uv run hyrule-knowledge quality --check
• uv run hyrule-knowledge ledger --check
• uv run hyrule-knowledge ledger lifecycle --check
• uv run mypy --strict src
• uv run hyrule-knowledge scan-secrets okf exports reports evals ledger schema

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a3ca3dd231

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Match common BGP snapshot low-disk wording

When the handoff is phrased by the incident itself, e.g. prevent BGP router snapshots from filling root filesystem or low disk on noc bgp-router-snapshot, disk_condition is false because these checks require either the exact low root filesystem wording or both filesystem and disk. Since snapshot_condition alone is not enough, those queries miss the new exact postmortem boost and return unrelated BGP/API or host refs instead of the curated retention context, so the new NOC low-disk coverage only works for the eval's narrow phrasing.

Useful? React with 👍 / 👎.