Skip to content

Add governed legacy inline-name cleanup - #394

Merged
witbrock merged 1 commit into
mainfrom
agent/legacy-inline-name-ui-cleanup
Aug 18, 2026
Merged

Add governed legacy inline-name cleanup#394
witbrock merged 1 commit into
mainfrom
agent/legacy-inline-name-ui-cleanup

Conversation

@witbrock

Copy link
Copy Markdown
Member

Outcome

Completes the browser-visible cleanup path for malformed legacy inline concept names left behind by the old identifier-title-casing fallback.

Changes

  • expose exact opaque selectors for legacy names[] rows
  • add an actor-bound governed DELETE /api/concepts/<id>/legacy-names operation
  • require a surviving canonical hasName, exact whole-array CAS, shared name locks, receipts, and canonical read-back
  • route the Concept-tab delete control to the exact operation and remove ambiguous predicate/text delete and edit fallbacks
  • preserve authored Unicode exactly and retain dir="auto"
  • document the new authority boundary

Validation

  • 88 focused and neighbouring ontology-authority tests passed
  • 17 focused frontend tests passed
  • edited Python modules compiled successfully
  • ESLint: 0 errors (13 pre-existing warnings in conceptTab.js)
  • independent security/concurrency review found no blocking defect
  • git diff --check passed

A separate pre-existing enrichment metadata-shape assertion remains red on current main; this patch does not touch that producer or assertion.

if concept_id:
resource_keys.add(f"ontology-concept-names:{concept_id}")
if method_name == "delete_legacy_name":
concept_id = _normalise_concept_id(arguments.get("concept_id"))
@witbrock
witbrock marked this pull request as ready for review August 18, 2026 11:47
@witbrock
witbrock merged commit bd06d5b into main Aug 18, 2026
4 checks passed
@witbrock
witbrock deleted the agent/legacy-inline-name-ui-cleanup branch August 18, 2026 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant