fix(build): repair team-sync + enterprise feature rot and gate them in CI

[runyourempire]

The problem

team-sync (AD-023, 17 commands) and enterprise (15 commands) are dormant command surfaces with zero frontend callers. CI built only default and experimental, so nothing ever compiled them — and they rotted silently into 56 compile errors. Enabling either feature was impossible.

This was found while auditing --all-features during #422 and is fixed here at the root, plus gated so it cannot recur.

Root causes

1. Dependency API drift (the real one-liner, hidden behind 33 cascading errors)

chacha20poly1305 0.10 → 0.11 moved to aead 0.6 / crypto-common 0.2, which removed the aead::OsRng re-export and AeadCore::generate_nonce. team_sync_crypto.rs failed at its import — so the module never compiled, so the #[tauri::command] macros in team_sync_commands never expanded, producing 33 cannot find __cmd__* errors that buried the actual cause.

Migrated to the Generate trait (XNonce::generate()) for the AEAD nonce, and rand::rngs::OsRng for x25519-dalek, which still pins rand_core 0.6. The two RNG generations are not interchangeable — verified against the vendored crate sources rather than assumed. Both are system CSPRNGs: this is an API migration, with no change to randomness source or strength. Deprecated XNonce::from_slice → TryFrom.

2. Named re-exports of Tauri commands

Both team_sync_commands/mod.rs and webhooks/mod.rs re-exported commands by name. #[tauri::command] emits a companion __cmd__<name> macro beside the function, and generate_handler! resolves module::__cmd__<name> — a named re-export carries the function and leaves the macro behind. Switched to glob re-exports, matching the working ace_commands/mod.rs.

3. rsa 0.10 test break

sso_crypto's test key generator passed rand::thread_rng() (rand_core 0.6) to an API now requiring rand_core 0.10. Fixed with getrandom::rand_core::UnwrapErr(getrandom::SysRng) — getrandom is already a direct dependency, so no new crate.

Also

• 3× sort_by → sort_by_key(Reverse(..)); 3× Duration::from_secs → from_mins/from_hours (verified const-callable on the pinned 1.95.0 toolchain, not just local 1.97)
• 6 genuinely dead imports removed
• Dormant-by-design items carry an explicit #[allow(dead_code)] at their cfg-gated mod declaration, matching the convention already used for the stub modules. This suppresses lint noise on staged code — it does not suppress compile errors, which is the failure this feature actually had.
• OrgPolicies.ts regenerated by ts-rs — stale only because enterprise tests had never run

The structural fix

Three new legs in the validate matrix: team-sync, enterprise, and both together. The combined leg is not redundant — it is the only one that swaps the real audit module in for audit_stub, a third path neither single-feature leg covers. Without these, this rot simply recurs.

Verification — all five legs

Leg	clippy -D warnings	cargo test --lib
default	clean	4437 passed
experimental	clean	—
team-sync	clean	4489 passed
enterprise	clean	4549 passed
team-sync,enterprise	clean	4601 passed

cargo fmt --check: clean. 0 failures anywhere.

Note for reviewers

webhooks/tests.rs imported check_circuit_breaker but never used it — removed. That suggests a missing test for the webhook circuit breaker, which is reliability-relevant. Left as a follow-up rather than silently writing tests for a dormant surface in a build-repair PR.

[runyourempire]

Closes the original --all-features finding in full.

Verified on the rebased branch (0f7b0470, post-#421):

cargo check  --lib --all-features                  -> EXIT 0
cargo clippy --lib --all-features -- -D warnings   -> EXIT 0

On main this was 56 errors. So team-sync and enterprise were the only rotted features — the other dormant flags (ocr, archive, void-universe, sql-check, streets-execution, calibrated-sim, generate-sim-fixtures) all compile clean and needed no changes.

Worth noting for the reviewer: the new CI legs deliberately gate team-sync, enterprise and team-sync,enterprise individually rather than adding a single --all-features leg. --all-features would have caught the compile rot, but it can never catch a feature-interaction bug, because it only ever exercises the all-on combination. The team-sync-without-enterprise path is the one that surfaced the audit_stub::AuditLogParams dead-field issue, and that path does not exist under --all-features.