> **Status**: Accepted > **Plan**: plans/archive/plan-20260913-0258-repo-harness-test-skill.md > **Contract**: tasks/archive/contract-20260913-0417-repo-harness-test-skill.md > **Notes File**: tasks/archive/notes-20260913-0417-repo-harness-test-skill.md > **Checks File**: .ai/harness/checks/latest.json > **Last Updated**: 2026-09-13 02:58 > **Recommendation**: pass > **Review Rubric Version**: 2 > **Reviewed Subject SHA256**: sha256:2bca4413c4dce391aa5645739dca1cb7c57f83fbf96a3fdeb2839ba65eeb...
Scanned 9/21/2026
Install to Claude Code
npx -y skills add Ancienttwo/repo-harness --skill archive --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Archive?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ancienttwo-archive-a259a02b)More formats (shields.io, HTML) on the badges page.
> **Archived**: 2026-09-13 04:17
> **Related Plan**: plans/archive/plan-20260913-0258-repo-harness-test-skill.md
> **Outcome**: Completed
> **Lifecycle**: review
> **Parent Run ID**: run-20260913-0417
> **Archive Projection V1**: `plans/plan-20260913-0258-repo-harness-test-skill.md` => `plans/archive/plan-20260913-0258-repo-harness-test-skill.md`
> **Archive Projection V1**: `tasks/notes/20260913-0258-repo-harness-test-skill.notes.md` => `tasks/archive/notes-20260913-0417-repo-harness-test-skill.md`
> **Archive Projection V1**: `tasks/contracts/20260913-0258-repo-harness-test-skill.contract.md` => `tasks/archive/contract-20260913-0417-repo-harness-test-skill.md`
> **Archive Projection V1**: `tasks/reviews/20260913-0258-repo-harness-test-skill.review.md` => `tasks/archive/review-20260913-0417-repo-harness-test-skill.md`
# Task Review: repo-harness-test-skill
> **Status**: Accepted
> **Plan**: plans/archive/plan-20260913-0258-repo-harness-test-skill.md
> **Contract**: tasks/archive/contract-20260913-0417-repo-harness-test-skill.md
> **Notes File**: tasks/archive/notes-20260913-0417-repo-harness-test-skill.md
> **Checks File**: .ai/harness/checks/latest.json
> **Last Updated**: 2026-09-13 02:58
> **Recommendation**: pass
> **Review Rubric Version**: 2
> **Reviewed Subject SHA256**: sha256:2bca4413c4dce391aa5645739dca1cb7c57f83fbf96a3fdeb2839ba65eeb3051
> **Reviewed Subject Scope**: normalized-final-content
> **Reviewed Target Revision**: e3b93f0f1cbdaaf051f789e91e7d7564635453bf
## Human Review Card
- Verdict: accepted by owner after the bounded external review and its correction.
- Change type: code-change (shipped skill content and manifest registration).
- Scope: testing router, four references, one manifest entry, four existing test inventories, and the synchronized reference-config routing row.
- Oracle preservation: inventories gained one package; existing assertion semantics were retained.
- Review: gatekeeper passed `3665ec35`; the formal codex-plugin review raised one P2 about global discovery of source-only guidance. The parent fixed that scope boundary in `511eb4a8`, then the owner explicitly approved acceptance and delivery.
- Rollback: revert the resulting PR squash commit.
## Mode Evidence
- P1: the manifest owns registration; installer selection and host sync consume its catalog.
- P2: install/update projects host skills; public init disables host sync and owns repo-local adoption.
- P3: references describe source-checkout techniques; canonical testing policy remains in sprint-contracts.md, with downstream projects directed to their own tooling.
## Verification Evidence
- Final prepared run: `.ai/harness/runs/run-20260913T040125-88263-20260913-0258-repo-harness-test-skill.json`; 26 checks passed, zero failed, against `511eb4a8`.
- The contract's 18 executable checks passed with current-exact evidence, including its eight focused test files and required repository integrity checks.
- Temporary HOME smoke: minimal excludes the skill; full copies all five files to both hosts. The source-copy readback covered `c879d2a6`; subsequent changes only clarify prose and discovery scope.
- Downstream init: dry-run planned 103 operations; apply succeeded and created the harness policy. The fixture lacks source tests/helpers and scripts/check-ci.sh, confirming the need for the downstream boundary.
- Final verification consumed the prepared evidence without repeating tests.
## Acceptance Receipt Projection
> **Disposition**: user_waiver
> **Reviewer**: User
> **Source**: user-waiver
> **Actor**: ancienttwo
> **Reviewed Subject SHA256**: sha256:2bca4413c4dce391aa5645739dca1cb7c57f83fbf96a3fdeb2839ba65eeb3051
> **Reviewed Subject Scope**: normalized-final-content
> **Reviewed Target Revision**: e3b93f0f1cbdaaf051f789e91e7d7564635453bf
> **Verification Evidence SHA256**: sha256:7ac8fe093746637c33319c748156dd5afc170e69cf7e3e802b2caf2cd2ae90fa
> **Issued At**: 2026-09-12T20:15:34.562Z
- Summary: Owner approved the corrected testing-router subject 511eb4a8 after the one formal review: source-checkout scoping fixed, canonical verification passed, and remaining acceptance is owner acceptance rather than another external review.
- Findings: none
## Residual Risks / Follow-ups
- Final hosted CI is a delivery gate after workflow archive and push; the old PR head's green run is not evidence for this revision.
- This is source-entrypoint verification, not a packed release or live LLM downstream-routing evaluation. No release is included.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!