v1.2.0 roadmap

[chaksaray]

v1.2.0 scope

Two committed items, one conditional item pending an open design
decision, listed honestly as such rather than presented as three equal
commitments.

Committed:

• v1.2.0: add owasp_ast schema field #103 owasp_ast schema field
• v1.2.0: implement deprecation policy schema fields #104 Deprecation policy schema fields (merged/rejected status
  values, merged_into, rejection_reason)

Conditional, not yet committed:

• Design question: confidence_baseline is self-reported, no structural verification #98 confidence_baseline structural backing. Still an open design
  question between two directions (documentation-only vs. a real schema
  field), not yet decided. In scope for v1.2.0 only if resolved before
  the release; will not block the release if the decision isn't made in
  time, ships in whichever version it actually lands in.

Versioning note

Both committed items are additive, optional schema changes. Per
docs/specs/scaling-and-governance.md Section 2, that's a minor version
bump, 1.1.0 to 1.2.0, no breaking change to any existing record or
implementer.

Why this issue exists

A single place to see the real, current state of the next release,
rather than three items only discoverable by browsing all open issues
individually.