[milestone Milestone 3 ] `.github/`: Organization profile page renders product matrix from canonical asse...

[telleroutlook]

🤖 Auto-filed from milestone doc bullet.

Repo: WasmAgent/.github
Milestone: Milestone 3 — Ops Tooling & Generator Infrastructure
Bullet:

.github/: Organization profile page renders product matrix from canonical asset URL

Problem

The WasmAgent GitHub organization lacks a structured profile page that displays a product matrix. Organization profile pages (.github/profile/README.md) are the canonical landing page for GitHub organizations, but currently there is no mechanism to render a structured product matrix from a central source of truth.

Approach

Create a GitHub organization profile that renders a product matrix by fetching from a canonical asset URL:

1. Create .github/profile/README.md - The organization profile landing page
2. Add dynamic product matrix rendering - Use GitHub's markdown/comment syntax to embed content fetched from the canonical asset URL
3. Define canonical asset source - The matrix data should be fetched from https://raw.githubusercontent.com/WasmAgent/wasmagent/main/docs/project-index.json (or the appropriate canonical source as defined in the wasmagent repository)

The product matrix should display:

• Project name with link to repository
• Brief description
• Status (e.g., "public", "beta", "internal")
• Layer (e.g., "workloads", "infra", "tools")

Implementation Notes

GitHub organization profiles support rendering content through standard markdown. For dynamic content from an external URL, consider:

• Using a GitHub Action that periodically updates the profile README with content fetched from the canonical asset URL
• OR using markdown that references the asset directly if GitHub's rendering supports it

Files Expected to Change

• .github/profile/README.md (new file) - Organization profile page with product matrix
• .github/workflows/update-profile.yml (new file, optional) - GitHub Action to periodically sync product matrix from canonical source

Acceptance Criteria

1. .github/profile/README.md exists and is valid markdown
2. The README renders a product matrix on the WasmAgent GitHub organization profile page
3. The product matrix includes at minimum: project name, description, status, and layer
4. When the canonical asset URL (e.g., project-index.json in wasmagent repo) is updated, the profile reflects the changes (either through direct reference or GitHub Action sync)
5. go build ./... passes (if there is any Go code in this repo; otherwise this criterion is N/A)

Notes for the implementer

This issue was auto-created by SweepMilestoneBulletToIssue (part of the
roadmap-autonomy family #220-#223). The bullet text above is verbatim
from the milestone doc — if it is ambiguous or too large for a single
implement cycle, the verify-first judge should return NEEDS_SPLIT (#214)
with sub-issue proposals or NEEDS_HUMAN (#216) with the blocker.

---

Filed automatically.

[telleroutlook]

🤖 This issue is being worked on.

• Bot ID: claude-bot-go-GreenCloud-BigMem-worker-2
• Job ID: 862
• Started: 2026-07-07T01:02:19Z
• Last heartbeat: 2026-07-07T01:09:20Z
• Lease expires: 2026-07-07T01:14:20Z

Another bot must NOT claim this issue while the lease is fresh (< 5 min since last heartbeat). If the timestamp above is > 5 min old, the bot has crashed and another bot may preempt.

[telleroutlook]

🤖 Auto-labeled panel-review by SweepAutoLabelMeta (Gap 4 of #183). This issue matches ≥2 meta-issue heuristics (large body / many issue references / architectural keywords / bot-authored). Worker will route to panel.Deliberate instead of the ordinary implement ladder.

[telleroutlook]

🤖 Closing: this milestone bullet describes work in a separate repository (erp-agent, wasmagent-ops, or trace-pipeline) that is not managed by the bot. WasmAgent/.github has been moved to discuss_only mode — implementation issues should be filed in the target repository directly.