Breaking changes **[controller]**

Controller 1.4.0 reworks the subscriber-identity and provisioning contract. A
management plane integrated against 1.3 must be updated, and the subscriber base
must be re-provisioned — these are not backward compatible.

The console in this release is already built against the new contract, so an
operator using the console needs to take no action beyond the re-provisioning
below. These matter to anyone driving the REST API directly.

• Subscriber records are keyed by an operator-assigned account identity and
  carry their locators explicitly, replacing the previous line-id keying. The
  subscriber base must be re-provisioned under the account model.
• The AAA source is selected at a new /bng/aaa endpoint. The previous
  open/gated mode field on the local-AAA configuration is removed.
• A live plan or status change is made by writing the subscriber record,
  which cascades into the running session. The separate per-session plan and
  revoke calls are replaced.
• Bulk provisioning request and response fields are renamed to the account
  identity.
• PUT /bng/session is now a partial merge — fields omitted from a request
  are preserved rather than cleared. A caller that relied on omission to clear a
  field must now clear it explicitly.

The controller's own release notes carry a migration checklist mapping each old
call to its replacement, and a Feature Integration Guide with the request and
response contract per capability. Both are the authority for integration work;
this section only states what breaks.