Provide metadata/manifest to distinguish internal tools from public products

[telleroutlook]

Cross-repo feature dependency

Filed by the cross-repo feature dependency patrol (opus) after analyzing open issues across the WasmAgent organization.

Dependency

• Blocked issue: Org profile project table lists internal ops and bot repos as public products #48 (Org profile project table lists internal ops and bot repos as public products)
• Blocking repo: WasmAgent/.github
• Required feature/API: Metadata API to filter internal vs public repositories
• Blocking issue: Org profile README truncates descriptions for internal tools .github#50

Analysis

Issue #48 in WasmAgent/wasmagent requires dynamically generating a project table that omits internal tools like claude-bot and wasmagent-ops. However, this filtering logic depends on WasmAgent/.github providing a machine-readable manifest or metadata flag (such as a 'public_product' boolean) in the org profile repository. Until the schema is extended in WasmAgent/.github to classify repositories, the table generator cannot accurately distinguish between public products and internal tools.

Acceptance criteria

• The blocking feature is available in WasmAgent/.github (shipped or has an open issue with claude label)
• The blocked issue Org profile project table lists internal ops and bot repos as public products #48 can proceed to implementation

---

Filed by automated cross-repo dependency patrol on 2026-07-01.

[telleroutlook]

🔧 Working on this — PR #50 created: #50

[telleroutlook]

✅ Implemented and merged in #50