chore(release): bump version to 6.2.3

[dwolfson]

Summary

Bumps the version to 6.2.3 (pyproject.toml, uv.lock), and updates the BACKLOG.md delete re-test item: the Egeria-blocked re-tests (ISSUE-146/147/117/125/132) move to the next release instead of holding this one.

PyPI's latest is 6.2.2, so 6.2.3 is free. Micro-tests pass (1144).

Release notes (to be added to the GitHub release)

release.yml auto-generates notes from PR titles, and #453's title doesn't mention ISSUE-148 or ISSUE-151. After the tag workflow creates the release, the section below goes at the top of its notes.

⚠️ Behaviour changes in 6.2.3

• AssetMaker action/process queries no longer filter to IN_PROGRESS by default (ISSUE-148). find_processes, get_processes_by_category, get_action_targets, get_actions_for_action_target, get_assigned_actions, get_actions_for_sponsor and get_actions_for_requester (sync and async) now default activity_status_list to None (no filter).
  • The old default silently dropped journal entries (which have no activity status) and every finished action.
  • If you want only open work, pass activity_status_list=["IN_PROGRESS"] explicitly.
• AutomatedCuration.get_engine_actions() has been removed (ISSUE-151). It called automated-curation/engine-actions, which the View Server doesn't provide, so it always failed with a 404. Use find_engine_actions("*") to list every engine action, or get_active_engine_actions() for only the active ones.

Highlights

• Analytic report specs (ISSUE-138/139/140/149):
  • A result's state envelope (measured / nothing found / not established / not applicable) is returned with every analytic output and shown as a chart subtitle.
  • Charts are drawn only for established answers (measured or nothing found).
  • New ActionParameter.analytic_binders builds non-JSON arguments, such as readers, from report-spec params.
  • AnalyticFunctionSpec gains optional manifest fields: kind, source, version, envelope, annotation_type, resource_types, family and tags.
• Dr.Egeria (feat(dr-egeria): Reference Data authoring + Valid Metadata family; fix ISSUE-142 #449):
  • Reference Data authoring commands.
  • Type-system valid values moved into a new Valid Metadata family.
  • 403 errors that aren't about authorization are no longer reported as "User not authorized" (ISSUE-142).
• Dr.Egeria Digital Products (ISSUE-145):
  • Agreement Type is retired (Egeria's AgreementType is deprecated; use Purpose).
  • Digital Subscription gains Service Levels alongside Support Level.
• Fixes:
  • Link Semantic Assignment now sends its status as termAssignmentStatus, so it reaches Egeria (ISSUE-144).
  • remove_note uses the Metadata Expert element delete, since Egeria has no note delete endpoint (ISSUE-146; the journal-entry delete itself still fails on Egeria's side).
  • Opt-in strict overview counts return None, not 0, when they can't be measured (ISSUE-123).
• Docs: the reference data / valid metadata guide is rewritten (docs: rewrite reference data / valid metadata guide; log ISSUE-143 #450). Newly logged Egeria-side issues: ISSUE-143 and ISSUE-147 (valid-metadata clears).

See PYEGERIA_ISSUES.md for each issue's details.

🤖 Generated with Claude Code