fix: map shipped-event portfolio targets

[saagpatel]

Summary

• Add Local Portfolio page IDs for portfolio-mcp, agent-session-replay, and mcp-trust.
• Route mcpaudit-web bridge receipts through the canonical MCPAudit project.

Validation

• uv run pytest tests/test_project_registry.py -q
• BridgeDB status healthy with actionable_unprocessed_shipped=0

Notes

• This PR only carries the durable mapping repair for shipped-event sync.

[chatgpt-codex-connector]

💡 Codex Review

GithubRepoAuditor/config/project-registry-overrides.json

Line 9 in 0b8afd6

"mcpaudit-web": "MCPAudit",

Mirror mcpaudit-web in default overrides

This repair only updates the JSON config, but src/project_registry.py still documents and uses DEFAULT_OVERRIDES as the fallback when overrides_config_path is missing or None. In that reduced/configless path, mcpaudit-web remains unresolved even though this commit is meant to route those bridge receipts to MCPAudit, so please add the same entry to the built-in defaults as the surrounding overrides are mirrored.

---

GithubRepoAuditor/scripts/build_demo_artifacts.py

Line 383 in 0b8afd6

"schema_version": "0.7.0",

Keep fixture truth on a valid schema contract

Changing the fixture snapshots to advertise the real 0.7.0 portfolio-truth contract makes output/demo/portfolio-truth-latest.json look safe for 0.7.0 validators/readers, but this builder still emits demo-shaped fields that violate that contract, such as audit-tier declared.lifecycle_state values (shipped/functional/wip), declared.category values like demo-product, derived.activity_status as current, and derived.primary_context_file as README.md. In contexts that validate or branch on schema_version, the public fixture will be rejected or treated as malformed; either keep the demo-specific schema version or normalize these rows to the real 0.7.0 enums.

ℹ️ 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".