Skip to content

epic: readme - Coordinate README audit coverage and refresh boundaries #540

Open
0 of 5 issues completed

Description

@ashleyshaw

Epic Summary

Coordinate the README audit for lightspeedwp/ThisOneTimeOnAcidCom: establish complete coverage, confirm findings and agree refresh boundaries before implementation.

The actual audit belongs in a dedicated child issue beneath this epic. This epic coordinates and accepts that outcome rather than performing duplicate implementation.

Linked Child Issues/Stories/Tasks/PRs

Parent: #531.

Planned child: the README coverage and findings audit; not yet created.

Existing blocked implementation issues:

Keep their existing parents and blocking relationships unchanged.

Milestones & Timeline

No deadline, milestone or estimate proposed. Agree audit findings and permitted refresh boundaries before affected implementation begins.

Acceptance Criteria

  • The audit child’s outcome is reviewed
  • Every baseline README and inventory change has a traceable disposition
  • Suspected defects are distinguished from confirmed findings
  • Existing-work boundaries prevent duplicate implementation
  • Permitted corrections are mapped to implementing work
  • Missing ownership, permissions and handoffs remain explicit
  • Epic completion receives a separate human decision

Dependencies / Blockers

Retain existing blocking links to #543 and #544.

Protected guideline READMEs require coordination with existing work and appropriate human approval. Manifest repair remains outside scope.

Creating the audit child does not authorise repository edits or command execution.

Additional Context

Use the earlier 20-README inventory at revision
0423fb8 as historical evidence.
Reconcile inventory changes and confirm the 16 suspected fence defects.

The audit ledger must record each path, purpose, evidence revision, findings,
disposition, overlapping work, approval requirements and verification method.

Branch instructions

Not applicable to this coordination epic. No branch or repository file changes are proposed. An epic must not become a PR development or closing target.

Definition of Ready (DoR)

  • Coordination goal and scope defined
  • Existing parent and blocked work verified
  • Audit scope and dependencies identified

Definition of Done (DoD)

  • Audit child outcome reviewed
  • Findings, dispositions and implementation boundaries recorded
  • Required implementing work mapped
  • Outstanding scope and handoffs reviewed
  • Separate human completion decision recorded

Overlap register

These existing records retain their scope; no changes to them are proposed.

Existing scope Boundary for these drafts
Root branding/testing and tooling/structure guidance Audit assigns residual passages; no competing rewrite
Protected guidelines Coverage and coordination only
Journal README/schema/publication guidance Only agreed residual README corrections
Prompt catalogue and compatibility notices Preserve delivered work
Report history, Claude environment, Discussion and task-document guidance Confirm passage ownership before edits
Proposed new .github/README.md Excluded

Checked directly overlapping issues: #453, #416, #107, #408, #266, #463, #449, #456, #263, #246, #255.

Metadata

Metadata

Assignees

Labels

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions