Repository navigation
Fully delete devantler-tech/actions after verified consumer migration #240
Description
🤖 Generated by the Agentic Engineer
Outcome
devantler-tech/actions was fully deleted on 23 October 2026 after the maintained consumer migrations, protected configuration withdrawal and private recovery backup were verified. This is deletion, not archival. The old repository identity was 948529001, with final default-branch commit ea4df9004d4ab43b6c9af5b0c5f55712f7211328.
Acceptance criteria
- Complete paginated organization, workflow/action source-closure and effective native-protection inventories found no active external portfolio dependency on Actions and no required workflow associated with its repository ID. All observed sources were resolved; private identities were not published.
- Open issues were transferred and open pull requests closed (Freeze devantler-tech/actions once the catalogue lives in .github #236); the final issue/pull inventory contained no open work.
- Maintained callers, signing approvals, verification policies and runtime helpers were delivered with ordinary qualifying consumer runs and signed-publication proof before deletion. KHoist's original migration Repoint organization-required workflows from actions to .github #237/Repoint the remaining consumers from actions to .github #239 prerequisites and khoist#468 are delivered; the independent database-flake issue khoist#464 remains open and is not claimed fixed.
- A private full-history mirror/bundle and tracker/release context were preserved. All live refs were rebound to the backup, the bundle and checksum verified, and recovery limitations documented. Git recovery does not promise restoration of the deleted GitHub identity, hosted metadata, permissions, secrets or historic run artifacts.
- Reviewed GitOps recreation controls were withdrawn through fix(config): withdraw legacy Actions management #721/v12.0.1 and observed absent with retained-resource positive controls. Deletion was followed by authenticated 404 responses for both slug and repository ID, authenticated maintained-repository positive controls and a complete organization census excluding Actions.
- Active portfolio registrations, website references, inventory entries and the obsolete coverage exception were removed without disabling drift/safety checks. Delivered through monorepo#4456, business-site#292/chore(deps): bump actions/upload-code-coverage from 1.2.0 to 1.4.2 in /actions/upload-coverage #298 and fix(coverage): finish legacy Actions retirement #728.
-
profile/andworkflow-templates/retain maintained sources and no legacy Actions dependency; profile rendering/navigation and catalogue/reference regression controls were checked.
Delivery evidence
- Deletion receipt and recovery boundary. The complete post-delete census contains 23 repositories, no Actions or Maintenance repository and no archived repositories. The separate latest-100-runs check is bounded, not a claim about every historical run.
- Canonical engineering guidance shipped in agent-skills v1.27.1 and agent-plugins#590/chore(deps): bump step-security/harden-runner from 2.22.0 to 2.22.1 #589. Both plugin PRs are protected-merged, with normal postmerge validation and scoped producer execution verified; no installed runtime cache was edited.
- Catalogue cleanup docs: clarify catalogue ownership and references #724 is protected-merged with complete native validation, resolved review and consistent action/workflow navigation and collapsibles.
- Final retirement correction fix(coverage): finish legacy Actions retirement #728 is protected-merged at
3bc75c3a147f40ccdfee9a63602d15570f8af3b1, with valid commit signature, main CI, normal release, normal CD and the complete live governance audit all successful. - Independently verified the anonymous exact-digest v12.0.2 signature for
ghcr.io/devantler-tech/github-config/manifests@sha256:4b759a1843df2d8d980da880f7ae8709da55a8ebe12d83a6fc65caa48fefad97, bound to that merge and normal CD run. Read-only live observations confirmed this exact revision Ready/applied by its source-bound reconciliations and all four withdrawn management resources still absent.
The private recovery backup is intentionally retained. Separate workflow-organization and CI-performance work remains tracked under #287 and its owner-repository issues; those are not unresolved Actions deletion gates.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Projects
- Status
Activity
feat!: import the devantler-tech/actions catalogue (#243)
devantler commentedon Oct 2, 2026
Refreshed the archival gates on 2026-10-02. Legacy Actions is still public and unarchived. Complete native inventory finds zero open PRs and one open issue, actions #1389, which intentionally tracks a necessary release backport of catalogue #389 while consumers remain on the legacy source.
Required-workflow readback still points five workflow families at legacy Actions (#237), and catalogue CD still calls its publisher (#242). These are active dependencies, so neither the consumer nor inventory acceptance gate is met. The backport issue needs delivery or an explicit migration disposition; it is not obsolete metadata to close blindly.
Blocker: required-workflow and publisher migration, legacy issue disposition, and declarative lifecycle/profile verification. Archive only after those gates have readback evidence.
devantler commentedon Oct 4, 2026
Verified retirement prerequisites — 2026-10-04
The native paginated legacy intake is empty: zero open issues and zero open pull requests, re-read at 11:13 UTC. The repository remains active and public. This completes the intake prerequisite, not the archive gate.
The complete public metadata census still finds 62 direct legacy declarations in 18 consumers and 70 legacy required-workflow declarations across 22 public default branches, rebound through 11:17:32 UTC. Administrative organization-ruleset coverage remains UNKNOWN under the current authority. Canonical publisher acceptance also remains blocked by #242. Archiving now would break required checks and publishers.
After #237, #239 and #242 clear, join the final complete active universe with source/rule/publisher evidence and known positive controls. Apply the reviewed three-phase archived-repository lifecycle, then read back the repository's archived state and verify profile and workflow-template behavior. No archive or settings change was made in this observation.
[-]Archive devantler-tech/actions once nothing references it[/-][+]Fully delete devantler-tech/actions after verified consumer migration[/+]chore: agent-claim #240 nonce=c521718ae0378db022ad0f32ce08507d
chore: agent-claim #240 nonce=bf65a66fe29c81b2250f092ea3c0fec0
devantler commentedon Oct 23, 2026
The maintainer-authorized repository deletion is now verified, not merely planned or archived.
devantler-tech/actions, repository ID948529001, default sourceea4df9004d4ab43b6c9af5b0c5f55712f7211328, with no open work; the most recent 100 workflow runs contained no active entry. The complete refreshed consumer/effective-policy census found no external executable dependency or required-workflow association with that repository.actions, nomaintenance, and no archived repositories.The remaining correction removes the now-stale temporary coverage exemption and updates current documentation. Its regression controls require an accidentally recreated
actionsrepository to be reported as UNDECLARED; historical signer identities and recovery safeguards are retained. #240 stays open until that correction is protected-merged and its normal live governance audit succeeds.chore: agent-claim #240 nonce=d90b0d0f47c8cadd81a93cb018720c02