Runtime triage: repository landscape fragmentation and duplicate DAIOF surface

[NguyenCuong1989]

Finding

GitHubAgent observed repository fragmentation during runtime orchestration probe.

Evidence

• Canonical repo: NguyenCuong1989/DAIOF-Framework
• Near-duplicate public repo: NguyenCuong1989/DAIOF-Framewor
• Several empty or backup-like repos detected: Library, multi_setup_backup_20251006_204547, hyperAI, sturdy-lamp, etc.
• Some large fork/source repos exist: vscode, vscode-docs, circleci-docs, brew.

Risk

• Source-of-truth confusion
• Doctrine drift
• Deployment target ambiguity
• Agent routing may pick wrong repo
• Human/AI execution errors increase

Proposed handling

1. Mark DAIOF-Framework as canonical in runtime registry and README references.
2. Inventory near-duplicate repos without deleting anything.
3. Add repository classification labels: canonical, archive, backup, fork, experiment, empty.
4. Do not delete or rename repos until explicit approval.
5. Update Sync Daemon route rules to refuse non-canonical DAIOF repo unless explicitly targeted.

Risk class

R2/R3 planning issue only. No destructive action performed.