feat: adopt ACF in homedir — test stack-audit and label-metadata against existing SDLC pipeline

[VECTORG99]

Summary

Adopt ACF in homedir to test the stack-audit and label-metadata phases in a real autonomous SDLC pipeline. homedir already has issue-metadata-validation CI, scc-* labels, and an autonomous worker — ACF should complement, not replace, these systems.

Context

• ACF repo: https://github.com/VECTORG99/acf
• homedir architecture: ARCHITECTURE.md (Quarkus/Go dual-stack)
• homedir skills: .agent/skills/homedir_expert/, .opencode/skills/wos-cycle/, .opencode/skills/wos-delegation/
• homedir CI: .github/workflows/issue-metadata-validation.yml (validates issue labels on create/edit)
• homedir templates: .github/ISSUE_TEMPLATE/autonomous-implementation.md
• ACF stack-audit: skills/02-stack-audit/SKILL.md
• ACF label-metadata: skills/06-label-metadata/SKILL.md
• Coordination issue: feat: adopt ACF in artemisa and homedir for testing #1

Motivation

homedir is the ideal testbed for ACF's stack-audit because it already has:

1. An autonomous SDLC pipeline with a 3-minute worker timer
2. Issue metadata validation CI (Python script checking labels)
3. A label taxonomy (scc-* labels, ready-to-implement, needs-metadata)
4. WOS multi-agent delegation (opencode, claude, antigravity)
5. 700+ issues and 1200+ PRs of historical data to audit

The question isn't "does ACF work in theory" but "does ACF's stack-audit find orphan PRs and escaped issues that homedir's existing systems miss?" If ACF finds gaps that the existing CI doesn't catch, that's immediate value. If it finds the same gaps, ACF is redundant. If it finds nothing, ACF's stack-audit is broken.

From an AI engineering perspective (30+ years watching systems fail): the only honest test is against a system that already has its own checks. Testing against a greenfield project tells you nothing — everything works on empty repos.

Affected Files (in homedir — tracked here, executed there)

• homedir/.devin/skills/ or homedir/.opencode/skills/ — ACF installation
• homedir/.github/workflows/ — potential ACF-triggered workflow
• homedir labels — verify ACF canonical labels coexist with scc-* labels

Constraint: This issue lives in the ACF repo. All file changes happen in homedir via separate PRs there. This issue tracks the adoption plan and results.

Acceptance Criteria

• ACF installed in homedir via ./install.sh /home/vector/Proyectos/homedir --agent opencode
• ACF canonical labels created in homedir (if not already present):
  • area:backend, area:frontend, area:ci, area:docs, area:security, area:devops
  • Verify these don't conflict with existing scc-* labels
• Stack-audit run on homedir:
  • gh pr list --state open → check for orphan PRs (no Closes #N)
  • gh issue list --state open → check for stale issues (ready-to-implement, no PR)
  • gh pr list --state merged --limit 50 → check for close gaps (merged PR, issue still open)
  • gh issue list --state closed --limit 50 → check for escaped issues (closed, no merged PR)
• Results compared against homedir's existing issue-metadata-validation CI:
  • Does ACF find gaps that the CI doesn't catch?
  • Does ACF's label taxonomy align with or conflict with scc-* labels?
  • Is ACF's stack-audit output more or less useful than the CI output?
• Findings documented in a comment on this issue:
  • What ACF found
  • What homedir's existing systems already caught
  • Where ACF adds value vs redundancy
  • Recommended adjustments to ACF based on homedir's patterns
• If ACF's label taxonomy conflicts with homedir's scc-* labels, document the conflict and propose a resolution (e.g., ACF labels as a superset, or a mapping table)

Validation

• gh issue list --repo VECTORG99/homedir --label "area:backend" returns results (labels exist)
• ACF stack-audit output is non-empty (it found something to report)
• homedir git status is clean after ACF installation (ACF is additive)

Complexity

Medium — installation is trivial (./install.sh), but the audit comparison requires understanding homedir's existing CI and label system.

Notes

• homedir's issue-metadata-validation.yml already checks for required labels on issue create/edit. ACF's stack-audit is broader: it checks the relationship between issues and PRs, not just issue metadata.
• homedir's autonomous-implementation.md template is very similar to ACF's issue-contextualized.md template — compare them and document differences.
• The scc-* labels (scc-ready, scc-failing-checks, etc.) are homedir-specific. ACF's labels (priority:P0-P3, area:*) are generic. They should coexist.
• This is a Phase 2 (Beta) issue per the roadmap — real-world testing.