Skip to content

Phase 4: Validation & Testing — Repository Restructuring #1599

Open

Description

@ashleyshaw

Summary

Follow-up work for PR #1534 governance feedback.
Part 2: Content and audit data reconciliation.

Outstanding Items

1. Reconcile Audit Inventory Counts

File: .github/projects/active/repo-restructuring-2026-07-25/INSTRUCTION_FILES_AUDIT_2026-08-05.md
Lines: 12-20
Issue: Summary counts don't align with detailed breakdowns
Fix Required:

  • Define whether archived files are nested within or separate from repo-local files
  • Update totals for file counts, line counts
  • Update percentage calculations

2. Align Schema Count Definition

File: .github/projects/active/repo-restructuring-2026-07-25/SCHEMA_AUDIT_REPORT.md
Lines: 11-16
Current State:

  • .schemas/ currently contains 23 files
  • Missing: agent-config.example.md, examples/ folder
    Fix Required:
  • Define what constitutes 'complete' schema coverage
  • Document missing files
  • Update executive summary to match core-schema count

3. Update Migration Matrix Paths

File: .github/projects/active/repo-restructuring-2026-07-25/SCHEMA_AUDIT_REPORT.md
Lines: 255-263
Issue: Inconsistent path references and alignment status
Fix Required:

  • Align with surrounding migration rows
  • Update target and current paths consistently

4. Reconcile Agent Totals

Files: CLAUDE.md (lines 344-351), AGENTS.md (lines 68-72), .github/custom-instructions.md (lines 42-45)
Issue: Inconsistent agent counts across documents
Verified Total: 19 spec-based + 16 multi-file agents
Fix Required:

  • Update all three documents to reflect consistent totals
  • Verify tier classification (Tier 1 vs Tier 2)

Dependencies

Related PRs

Priority

Medium - Governance documentation accuracy and consistency


Definition of Ready (DoR)

  • Clear problem statement and expected outcome
  • Acceptance criteria defined
  • Related issues/dependencies identified
  • Required resources/approvals listed

Definition of Done (DoD)

  • All acceptance criteria met
  • Changes tested and validated
  • Documentation updated
  • Changes merged and deployed
  • Stakeholders notified

Activity

  1. self-assigned this
    on Aug 5, 2026
  2. linear-code commented on Aug 5, 2026

    @linear-code
  3. ashleyshaw commented on Aug 7, 2026

    @ashleyshaw
    MemberAuthor

    📋 Project Planning Update — repo-restructuring-2026-07-25

    This issue is related to the repo-restructuring-2026-07-25 active project.

    📁 Project Documentation

    ✅ Project Status

    Planning and OpenSpec RFC generation for this project are complete. Documentation is available in the project directory.

    🎯 Next Steps

    Refer to project documentation for:

    • Implementation timeline and roadmap
    • Success criteria and validation steps
    • Resource requirements and dependencies

    🔗 Resources


    Co-Authored-By: Claude Haiku 4.5 noreply@anthropic.com

  4. github-actions commented on Aug 9, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 3 day(s)
    • SLA state: Within SLA
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-08-09T11:40:24.014Z

    Maintained by project-meta-sync workflow.

  5. added this to the v1.1 milestone on Aug 29, 2026
  6. github-actions commented on Sep 8, 2026

    @github-actions
    Contributor

    ⚠️ Bare Labels Detected

    This issue has labels that are not in the canonical taxonomy:

    • migrate:priority:important
    • migrate:status:ready
    • migrate:area:infrastructure
    • migrate:type:task

    Valid Canonical Labels

    Please use labels with a prefix from the canonical taxonomy:

    • Type: type:bug, type:feature, type:task, type:documentation, etc.
    • Status: status:needs-triage, status:in-progress, status:done, etc.
    • Priority: priority:critical, priority:high, priority:normal, priority:low
    • Area: area:ci, area:docs, area:labels, area:security, etc.
    • Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

    For the complete list, see .github/labels.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Fields

Priority

None yet

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions