fix(identity): map shipped operator surfaces

[saagpatel]

Summary

• map operator-os-explainer to its verified Local Portfolio page
• canonicalize claude-harness-modernization to the existing claude-code-harness surface
• pin both mappings with a focused registry regression test

Verification

• .venv/bin/ruff check tests/test_project_registry.py
• .venv/bin/pytest tests/test_project_registry.py -q
• git diff --check

Scope

Identity/catalog mapping only. No product code, lifecycle expansion, deployment, or public operator-os branch history changes.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f810fa7f46

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Sync the seam-linter with the new harness alias

When bridge/session/notification identity events emit claude-harness-modernization, this new registry override resolves in project-registry, but operator-os-seam-linter --identity-resolution still won't see it: the inspected linter builds its resolver from IDENTITY_ALIAS_MAP and DEFAULT_SUPPLEMENTARY in src/operator_os_seam_linter.py, not from this config, and DEFAULT_SUPPLEMENTARY was not updated. Please either update the linter/default alias source or make the linter consume the same configured mapping so the regression gate covers this shipped harness alias.

Useful? React with 👍 / 👎.