Infrastructure Discovery: split "Exploring Inventory" into Graph and Security pages

[claude]

Requested by Anastasiia Popova · Slack thread

Before / After

Before: the Infrastructure Discovery section had a single "Exploring Inventory" page covering both the resource graph and the security posture content, while the Wallarm Console UI already presents them as two separate top-level tabs.

After: docs match the current UI with one page per tab. Nav order is now Overview, Setup, Graph, Security, Attack Paths (unchanged: Overview, Setup, Attack Paths).

• Graph (infrastructure-discovery/graph.md) — the former "Graph" section: the relationship graph, filters, results panel, node details. Reuses the existing graph-detail.png screenshot.
• Security (infrastructure-discovery/security.md) — the former "Security" section in full: Assets, Findings (including blast radius and AI-assisted enrichment), Drift Events, Policies, Rules. Reuses all existing screenshots for those sub-tabs.

No product-logic changes — this is a content reorganization only, per Anastasiia's request. All prose is carried over from the existing page; only the intro paragraphs on each new page are new, written to match the tone of the existing Overview/Setup/Attack Paths pages.

How

• Added docs/latest/infrastructure-discovery/{graph,security}.md, removed exploring.md.
• Added/removed matching one-line --8<-- wrappers in docs/6.x/ and docs/7.x/ (Infrastructure Discovery does not exist in docs/5.0/, left untouched).
• Updated nav in mkdocs-6.x.yml / mkdocs-7.x.yml, the homepage cards in docs/6.x/index.md / docs/7.x/index.md, and the llms.txt indexes for both versions.
• Fixed inbound cross-links in attack-paths.md and setup.md that pointed at exploring.md / #graph / #security / #findings / #policies.
• Added redirects in docs/6.x/_redirects (the active root version's file, with both bare and /7.x/-prefixed rules) from the old exploring/ path and its anchors to the new graph/ and security/ pages and anchors.

Verification

• Clean venv, pip install -r requirements.txt, git submodule update --init --recursive.
• zensical build -f mkdocs-6.x.yml and -f mkdocs-7.x.yml — both clean, no issues.
• scripts/generate_raw_markdown.py for both configs, then scripts/check_markdown_companions.py site — 636 pages checked, 3 exempt, 0 missing.
• scripts/check_redirects_budget.py docs/6.x/_redirects — 272 rules, 24 charged against the 100 cap.
• Manually inspected the built site/ HTML for both new pages: correct titles, all seven Security sub-section anchors present, and cross-links between Graph/Security/Attack Paths resolve to the right relative URLs (../graph/, ../security/, ../security/#findings, ../security/#policies).

Note on checks: the four red checks (deploy/netlify, "Pages changed", "Header rules", "Redirect rules") are a known-stale retired Netlify integration left over from before the move to Cloudflare Workers — not a real failure. The authoritative check is Workers Builds: wallarm-docs.

---

Generated by Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	wallarm-docs	14ad5b4	Aug 28 2026, 10:36 AM

[claude]

Requested by Anastasiia Popova · Slack thread

Standing down on the Workers Builds: wallarm-docs failure on this PR (build 6c9f29cd-acd0-43ca-a675-f7c794e1c2d8, commit 14ad5b4) rather than guessing at a fix.

• Reproduced the exact production build Cloudflare runs for this branch — scripts/build.sh with CONTEXT=production, matching the script's own SKIP_IMAGE_OPTIMISATION=1 behavior for any non-master branch — under a fresh venv on Python 3.13.12 (the version pinned in .python-version). All four versions (6.x, 7.x, 5.0, deprecated) built with "No issues found," 911 pages checked with 0 missing markdown companions, and the redirects budget at 24/100 charged. This diff does not reproduce the failure locally.
• Checked whether this is a broader outage: master's current HEAD (f4ab1b1) shows Workers Builds: wallarm-docs = success (completed 2026-08-27T23:25:29Z), so it is not a blanket Cloudflare-side failure affecting every build right now. The failure looks specific to this branch/build, but nothing in the diff or the local reproduction points to what would cause it.
• I don't have access to the Cloudflare dashboard build log from this session (dash.cloudflare.com is blocked here) and no way to trigger a retry without pushing a new commit.

Could someone with dashboard access check the log for build 6c9f29cd-acd0-43ca-a675-f7c794e1c2d8, or retry it? I'll act on whatever it shows.