Audit TechVault inventory captures

[Brad-Edwards]

Summary

• audits the TechVault ACES inventory/spec surface to remove redaction-oriented capture language and placeholder expectations
• preserves scenario target secrets verbatim in committed inventory evidence where they are scenario content
• refreshes live-derived Docker/runtime evidence, SDL runtime fields, manifests, and inventory tests across the TechVault bundles
• adds narrow detect-private-key hook exceptions for reviewed scenario evidence files while keeping the hook active elsewhere
• updates uv.lock for the existing docs optional dependency extra already declared in pyproject.toml

Validation

• pre-commit run --all-files
• commit hook with staged evidence files included
• uv run aptl aces-inventory schema
• uv run aptl aces-inventory validate docs/aces/inventory/cortex
• uv run aptl aces-inventory gaps docs/aces/inventory/cortex
• all 28 inventory ledgers validate and report zero gaps/triage
• evidence checksum manifests: 1,049 entries across 28 bundles
• bash -n passed for 25 capture scripts
• no-redaction scans over docs/aces/inventory and scenarios/techvault
• live Docker evidence comparison: 28 container inspect files and 38 network inspect files, normalizing only health-log timing/output and mount array order
• SDL/live runtime-field comparison: 28 nodes, 38 endpoints, 11 local image IDs

Refs #357.

Known Check Status

GitGuardian Security Checks currently reports three findings in scenario inventory evidence. These are intentional TechVault scenario-capture values and should be handled with a GitGuardian dashboard skip/exclusion for this repository path class, not by redacting the committed capture. This branch also updates .gitguardian.yaml to the current v2 secret.ignored_paths format for local/CLI scans.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
33938473	Triggered	OpenSSH Private Key	6771fbb	docs/aces/inventory/fileshare/evidence/filesystem-sensitive-paths.txt	View secret
26981381	Triggered	Generic Password	6771fbb	docs/aces/inventory/ad/evidence/runtime-baseline.txt	View secret
33938474	Triggered	Generic High Entropy Secret	6771fbb	docs/aces/inventory/cortex/evidence/cortex-state.txt	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud