You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cleanup: remove guard CLI flags, auto-detect DIFC from policies
Remove --enable-guards, --enable-config-extensions, --session-secrecy,
and --session-integrity CLI flags. Guards are now auto-enabled when an
allow-only policy is detected in the configuration.
Changes:
- Remove EnableDIFC field from config.Config
- Remove SessionConfig struct and session label parsing
- Remove enableDIFC, enableConfigExt, sessionSecrecy, sessionIntegrity
flag variables and their env var defaults
- Auto-detect DIFC in NewUnified() after guard registration: enabled
when any non-noop guard or global policy override is present
- Add HasNonNoopGuard() to guard.Registry for auto-detection
- Move guards status logging into NewUnified() (before backend launch)
- Always skip strict JSON schema validation for extension fields
- Change requireGuardPolicyIfGuardEnabled to warn+noop fallback
instead of fatal error
- Fix flaky integration tests: replace hardcoded ports with dynamic
allocation via getFreePort(t)
- Update guard-policies docs to use canonical allow-only format
- Update scripts to remove all references to removed flags
- Update DIFC_RULES.md, config.example.toml, OVERVIEW.md
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
cmd.Flags().StringVar(&difcSinkServerIDs, "guards-sink-server-ids", getDefaultDIFCSinkServerIDs(), "Comma-separated server IDs whose RPC JSONL logs should include agent secrecy/integrity tag snapshots")
0 commit comments