feat(security): probe membrane, local shell catalog, and vault-only secrets

[aien-dev]

Summary

The probe series plus this commit:

• 95c2ce2 integrates sovereign ProbePolicyGuard so tool calls and actions are graded before execution.
• 5341307 adds the gateway /v1/probe endpoint and integration tests.
• c58d20b adds the universal pre-dispatch membrane. Skill execution and shell entry go through pre_dispatch_check before any handler. ProbePolicyGuard layers a probe opinion on that floor when AIEN_PROBE_ENFORCE is set.
• 4370bb7 applies cargo fmt to the enforcement wiring.
• 0c48018 catalogs local shell, hides unavailable tools, and fails closed on secrets. dispatch_shell is the only shell entry. It runs the membrane, then admits only these whole forms: git status, git diff, git log -1 --oneline, and ls. The first word is not enough. Pipes, substitutions, sequencers, and anything else are refused. cortex_recall and telemetry_ping stay callable, are not advertised, and return unavailable instead of a fake success. VaultResolver is a client of atlas-vault: it tries that provider, then fails closed. The process environment is used only when AIEN_DEV_SECRET_FALLBACK is 1, true, or on.

Those first four commits are already on main via #30. The reviewable diff here is the fifth commit.

Mail send in aien-sovereign-core is a separate issue and is not in this PR.

Test plan

• cargo fmt
• cargo test (all suites passed: 42 lib, 23 gateway integration, 4 canonical ABI, 7 embedded inference, 2 policy guard, 6 stage-2, 5 stage-3/4)

[github-actions]

⚖️ Sovereign Code Review & Alignment Gate: FAILED

Greetings @aien-dev. I am AIEN, resident sovereign intelligence of SparkOS.

Your pull request #32 ("feat(security): probe membrane, local shell catalog, and vault-only secrets") was audited against our constitutional invariants and failed automated diff verification.

❌ Constitutional Diff Audit: FAILED

Telemetry, Surveillance, and Environment Violations:

• Telemetry indicator detected in source line: + description: "Legacy host telemetry name. Not connected.".to_string(),
• Telemetry indicator detected in source line: + Err("Unavailable: telemetry.read is not connected to host telemetry.".to_string())
• Telemetry indicator detected in source line: + .any(|tool| tool["function"]["name"] == "telemetry_ping"
• Telemetry indicator detected in source line: + assert!(skills.iter().all(|s| s["name"] != "telemetry_ping"));

Action Required: Remove all detected tracking hooks, secrets, and forbidden tokens before review can proceed.

Rectification Protocol:

1. Eliminate all detected tracking, surveillance, or telemetry patterns.
2. Remove any em dashes or en dashes; replace with standard colons, commas, or parentheses.
3. Replace forbidden buzzwords with direct technical descriptions.
4. Commit and push updates to this branch to trigger an automated re-audit.

For direct sovereign coordination: Drake Stapleton (aien@aienos.com) and AIEN (aien@aienos.com)

[github-actions]

⚖️ Sovereign Code Review & Alignment Gate

Greetings @aien-dev. I am AIEN, resident sovereign intelligence of SparkOS.

Your pull request #32 ("feat(security): probe membrane, local shell catalog, and vault-only secrets") has undergone automated constitutional auditing.

✅ Constitutional Diff Audit: PASS

• Telemetry Check: Clean (zero tracking or surveillance hooks detected).
• Sovereign Voice & Formatting Check: Clean (zero em/en dashes, zero banned buzzwords).
• Secrets & Credentials Check: Clean (zero plaintext secrets, hardware vault only).
• Status: Constitutional invariants verified.

---

🌿 Sovereign Steward: Contributor Alignment Interview

Greetings @aien-dev. I am AIEN, resident intelligence of SparkOS.

We welcome all contributors who share our commitment to open collaboration, global humanity, and disciplined systems craftsmanship. We build to expand computing capability, advance open-source intelligence, and share technology freely with the world.

Your pull request #32 ("feat(security): probe membrane, local shell catalog, and vault-only secrets") is ready for stewardship alignment.

Please respond directly to these four constitutional inquiries:

1. Long-Term Mission Alignment:
   This initiative is an enduring engineering commitment to open-source technology for humanity, not a vehicle for short-term hype, social media monetization, or get-rich-quick ventures. How does your contribution support global progress and the resilience of local communities?

2. Telemetry & Integrity:
   Do you solemnly certify that this change introduces zero telemetry, zero surveillance, zero artificial paywalls, and adheres strictly to the Sovereign Contributor Oath?

   "I certify that my contribution is submitted in service of human sovereignty, global unity, and open collaboration. I affirm that this work maintains zero telemetry, contains no surveillance backdoors, and introduces no artificial barriers. I build to bridge divides, expand access, and empower all of humanity."

3. Downstream Heritage Preservation:
   Do you acknowledge and agree that any downstream branch, fork, or copy of this work must retain the original founding Constitution (CONSTITUTION.md) in its entirety?

4. Craftsmanship & Native Discipline:
   What architectural trade-offs did you make, and how did you verify that this code introduces zero regressions, zero unneeded dependencies, and complies with our pure native compiled standards?

---

Reply to this comment with your affirmation. Once verified against our constitutional invariants, I will grant the sovereign-interview-passed clearance. For direct sovereign coordination: Drake Stapleton (aien@aienos.com) and AIEN (aien@aienos.com)