aiops: testing-agent - Consolidate shared skill resolution #1344

AI Ops Summary

Consolidate the Testing Agent’s active Tier 0 utility resolution onto shared root skills while preserving existing testing behaviour, safety boundaries and historical exports.

This is shared-skill governance and packaging—not a repeat of the completed Playwright migration or multi-framework expansion.

Linked records

• Linear coordinator: GIT-1190.
• Synced GitHub issue: lightspeedwp/.github issue 1344.
• Existing execution parent: GIT-1166, corresponding to lightspeedwp/.github issue 1320.
• Historical planning: lightspeedwp/.github issue 1316.
• Historical delivery: feat(playwright-testing-agent): performance routing, a11y/SEO/console gates, and scope-exclusion discipline #1392 and feat: Testing Agent Phase 2 — Multi-Framework Expansion (v2.2.0) #1945.
• Canonical packaging/validation epic: GIT-2735.
• Existing path/provider-parity work: GIT-2736.
• Existing package-metadata work: GIT-2737.

These description links do not create or change native relationships.

Evidence and limits

The recorded repository inspection used develop commit 65a013b25eb4f81806496965adad8e3f458a34e5; refresh it before implementation.

At that inspection, the root frontend skill and agent-attached copy differed only in footer content. This supports investigating shared ownership, but does not independently authorise deletion.

Historical PR delivery does not establish completion of this consolidation issue. Recorded parity-hook results also did not prove current-agent regression coverage: a test targeted a removed directory and could return early when its resource was absent.

No current implementation PR or fresh runtime success is established by this description.

Bounded scope

1. Inventory active Tier 0 consumers, manifests and provider references; separate them from retained historical inventories.
2. Compare complete skill packages, supporting resources, provenance and licences—not only their primary Markdown files.
3. Establish root skills/ ownership for genuinely identical shared functionality.
4. Update active resolution only after caller and loading evidence supports the change.
5. Preserve existing framework support, review-before-code, performance handoff and browser safety rules.
6. Allocate broader path/provider validation to test: testing-agent - Verify migrated paths and provider parity #3948 and package metadata reconciliation to aiops: testing-agent - Reconcile canonical package metadata #3949 rather than duplicating those scopes.

Acceptance criteria

• Active and historical references have an evidenced disposition.
• Shared package ownership and any justified agent-specific variant are explicit.
• Approved active consumers resolve the intended shared skill without broken manifests.
• Independent and agent-mediated loading evidence covers the agreed hosts.
• Existing framework behaviour and safety boundaries remain intact.
• Permission-denial and missing-resource cases fail explicitly.
• Provenance and retained-consumer compatibility are demonstrated before retirement.
• Focused results identify the inspected revision, commands and limitations.
• Any deletion or retirement receives separate approval.

Exclusions and delivery instructions

Do not repeat the delivered agent rename or framework expansion. Do not introduce a new Python framework, activate workflows or perform production rollout.

Reuse a matching implementation PR. Proposed branch remains aiops/testing-agent-shared-skill-resolution, targeting refreshed develop; verify current repository instructions and the live AI Ops PR template before use.

Preserve human ownership and scheduling metadata. Resolve PR assignment, labels and changelog disposition separately. Stack only where a demonstrated dependency and approved base/retargeting plan require it.

Close lightspeedwp/.github issue 1344 only after its bounded consolidation criteria are delivered. Do not automatically close execution parent issue 1320 or reopen completed planning issue 1316.

Reference correction and historical preservation

Earlier references incorrectly resolved historical identifiers #1344, #1320 and #1316 to unrelated cross-repository pull requests. The explicit .github issue URLs above supersede those references.

Retain the existing historical acceptance checklist, original steps, reported readiness, completion tracking and template caveat below this revised description. Historical checked items are not current readiness certification.

Historical acceptance criteria and steps

Retained as historical tracking, not newly certified.

• Deliverables for W7-C4 are implemented according to the Phase C plan
• Related agent manifests, skill references, and docs are updated where applicable
• Validation checks pass (lint/test/workflow checks relevant to this task)
• PR is linked and ready for review against the parent epic scope

Original steps:

• Confirm scope against the Phase C task breakdown; its original projects/active link is stale and the current reference is linked above.
• Implement Consolidate playwright-testing-agent to Tier 0
• Run the relevant checks for changed files/workflows
• Update project tracking docs and task status
• Open/update PR and link it back to this issue

Original reported readiness:

• Scope and expected outcome are defined
• Parent/related issues are linked
• Task is actionable and implementation-ready

These checked items preserve historical assertions, not current readiness certification.

Original completion tracking:

• Implementation completed and documented
• Relevant checks pass and evidence is attached
• PR linked and merged to develop (or queued for merge)
• Tracking docs updated with current status

Definition of Ready (DoR)

• AI ops goal described
• Area/action mapped
• Acceptance criteria listed
• Estimate added

Definition of Done (DoD)

• All acceptance criteria met
• Solution/automation verified
• Documentation updated
• PR uses correct branch prefix (aiops/)
• PR uses the correct PR template based on type:aiops PR label or linked issue type or linked issue type:aiops label
• Branch deleted after merge
• Linked issue(s) updated with latest status and closed after merge,
• The related epic should not be closed, instead updated with a comment to reflect the closed issue

Template check: live AI Ops title pattern automation: conflicts with approved aiops: title policy; use aiops:, do not change the template. Preserve its unchecked DoR/DoD; estimate readiness remains unresolved rather than inventing points.