open-risks.md

Open Risks and Inconsistencies

High Impact

1. GenerationSpec::strategy is not fully applied in UserAgentService.
2. UserAgentBuilder compatibility mapping is hardcoded and can drift from templates/filters.

Medium Impact

1. FilterInterface is implemented by filters that operate on BrowserTemplate; contract and usage are aligned.
2. UserAgentBuilder prints failed spec details to stdout in exception paths.
3. Seeded generation uses mt_srand, which mutates process-global random state.

Low Impact

1. LruHistory naming implies UA-level tracking, but AvoidRecentStrategy stores browser family keys.
2. RandomSpec and several GenerationSpec fields are validated but not fully reflected in generation behavior.

Not Verifiable from Current Code Inspection

• HTTP routing/controller layers.
• Queue/event/listener orchestration.
• Database persistence in generation path.

Next

• Documentation Hub

Related

• Dependency and Risk Notes
• Failure Cases
• Spec and Validation