docs: reference PR proving adopted UI quality policy on new develop base

[Paulo Lacerda (placerda)]

Problem and outcome

PR #144 adopted the new quality evaluator into the protected develop base
(merged ec18a73). docs/python-development.md still contained two stale
statements written before adoption: one claiming "the old protected checker
still rejects these changes until authorized adoption," and one claiming "the
reference PR remains missing." This PR corrects both statements to honestly
cite the incorporation, and itself serves as the reference PR: by opening it
against the current develop tip (which already contains #144), it forces
real CI to run against the adopted protected base rather than the pre-adoption
base exercised by PR #112 (closed) or stale workflow run 38065760672.

Type of change

• Documentation or engineering guidance

Related backlog item or issue

Independent human review of the recorded exception decisions remains
outstanding — see issue #695. This PR demonstrates base adoption only; it does
not close or complete that review.

Changes

• docs/python-development.md: replaced the stale "old checker still rejects
  until adoption" sentence with a statement that the new evaluator was
  adopted into develop by PR fix: make boundary diagnostics safe and simplify exception validation #144 (ec18a73), and the protected checker now
  applies it to subsequent PRs.
• docs/python-development.md: replaced the stale "reference PR remains
  missing" sentence to state that the initial PR (fix: make boundary diagnostics safe and simplify exception validation #144) reported a missing
  protected policy only because its base predated adoption, and that this PR
  is the reference PR exercising the adopted base.

Evidence

Check	Command or method	Result
Base adoption	Branch created from origin/develop tip ec18a73 (merge commit of #144)	Confirmed via git log/git fetch
CI on adopted base	Automated checks on this PR (quality-gate, container-tests, etc.)	See PR checks — pending at PR creation time, to be reported in follow-up
No ruleset/tag/release changes	No .github ruleset, tag, or release operations performed	Confirmed by diff scope (doc-only change)

Contracts, data, security, and accessibility

N/A — documentation-only change. No code, API, identity, session, or
persistence behavior is affected.

Cross-repository dependencies

• None

Documentation

This PR itself is the documentation update (docs/python-development.md).

Residual risks

• Independent human review of the 30 reviewed / 7 keep / 23 diagnostic
  correction decisions in .quality/exception-technical-review.json remains
  outstanding (issue #695) and is not resolved by this PR.
• CI results for this specific PR must be inspected after opening to confirm
  they reflect the new protected base rather than a stale cached run.

Checklist

• The change is scoped to the stated outcome.
• Tests protect affected behavior or contracts. (Doc-only; relies on repo's full CI gate running against new base.)
• Secrets, tokens, personal data, and private environment names are absent.
• Authentication, authorization, accessibility, migration, and recovery were considered where applicable. (N/A — doc-only.)
• CHANGELOG.md and affected documentation are updated. (This PR is the documentation update itself.)
• At least two reviewers are assigned when repository policy requires them.