Add GitHub stars and fork count as tracked objective metrics

[kai-linux]

Goal

Add GitHub stars and fork count as measurable metrics in objectives/agent-os.yaml and wire them into the outcome attribution and production feedback loops. The system currently optimizes only for internal operational metrics (success rate, escalation rate, completion time). It has no feedback signal for whether external adoption is growing. This closes the loop so the planner and scorer can see whether work is driving adoption.

Success Criteria

• objectives/agent-os.yaml includes a github_stars metric with appropriate weight
• A lightweight evidence exporter writes current star/fork counts to an evidence file (can use gh api to fetch)
• The production feedback artifact includes the current star count
• The outcome attribution can compare pre/post-merge star movement (even if noisy)
• Planner sees adoption signal alongside operational metrics

Why This Matters

The stated goal is "trusted adoption by technical builders." Stars are an imperfect but real proxy. Without measuring them, the system has no way to know whether any of its work is driving adoption. Every sprint becomes internal plumbing because internal metrics are the only ones visible.

Outcome Checks

• github_stars

[kai-linux]

🤖 Dispatched to orchestrator.

Task ID: task-20260404-130317-add-github-stars-and-fork-count-as-tracked-objecti
Project key: agent-os