Repository navigation
Fully remove the four archived portfolio repositories #679
Description
🤖 Generated by the Agentic Engineer
User Story
As a portfolio maintainer,
I want the four archived repositories (data-product, reusable-workflows, doggy-countdown and client-portal) fully removed,
So that obsolete products and automation are no longer retained as live GitHub repositories.
Acceptance Criteria
- Preserve private Git and tracker/release recovery material and state its limits.
- Check remaining executable dependencies and preserve any still-relevant work.
- Remove the three observe-only management records through a reviewed, normally published change and independently observe their withdrawal; never grant Crossplane Delete.
- Delete only the exact four archived repository identities after fresh verification.
- Verify authenticated absence by both slug and ID, a complete organization census and a live positive control.
- Update current portfolio documentation without deleting historical evidence.
Plan
Repository removal, management withdrawal and the final current-catalogue correction are complete. monorepo#4393 merged as c2111818cc71624a931344ca5dac2ec51e107288 and is included in current reviewed main. No active repository is included in this issue.
Part of #56.
Completion verified — 22 October 2026
The remaining documentation criterion is delivered. The effective portfolio map no longer lists the deleted standalone catalogue, the work-selection guide derives archived scope from live GitHub state, and the shared automation card directs new work to the maintained .github catalogue. The merged correction changes only those three current instruction files; historical evidence remains intact.
Exact-head CI 39552305128 completed successfully: all 106 jobs were collected across both pages, with 66 successful and 40 skipped. The actual Linux and macOS cleanup safety jobs both passed. All three post-merge workflows at the merged revision also succeeded. The complete current organization census excludes the four deleted repository names and retains the maintained catalogue as a positive control.
The earlier authenticated deletion and private-recovery receipt remains the evidence for the completed removal work; no deletion or recovery operation was repeated. monorepo#4394 remains open for its independent 15-minute feedback objective: the successful macOS cleanup job took 20 minutes 35 seconds. That performance target was not met and is not part of this issue's final documentation criterion; its stale blocking relationship is removed while its evidence and acceptance remain unchanged.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Projects
- Status
Activity
chore: agent-claim #679 nonce=794436648413d5f06b4a359f847c3ee0
devantler commentedon Oct 21, 2026
All four explicitly requested archived repositories have been fully deleted:
data-product,reusable-workflows,doggy-countdownandclient-portal.Management withdrawal merged in #680 and published normally as v7.23.1. Its publication run succeeded. Independent read-only observation confirmed the signed revision was current and the three observe-only records were absent before their corresponding repositories were deleted. No Delete management permission was introduced.
Each deletion returned HTTP 204. Subsequent authenticated lookups by both exact slug and numeric repository identity returned HTTP 404 for all four. A complete paginated organization census contained zero archived repositories, with the maintained shared catalogue still accessible as a positive control. The active
actionsrepository was not deleted by this operation.Private recovery material retains available Git history, branches, tags, pull-request heads and tracker/release context.
client-portalwas genuinely empty. These copies are not a complete restoration of GitHub service metadata, approvals, Actions artifacts, settings or credentials; those limits are recorded privately.The remaining catalogue-documentation correction is monorepo#4393. This issue remains open until that correction is delivered.
devantler commentedon Oct 21, 2026
The four repository deletions, signed management withdrawal, authenticated absence checks and private recovery verification are complete. Post-deletion platform health also passed.
The final factual catalogue correction, monorepo#4393, has a clean current-head review but is not merged: its macOS safety job exceeded the 15-minute feedback budget. monorepo#4394 now tracks that measured outlier without weakening any cleanup protection or deadline.
The native blocked-by relationship is recorded. This issue is back in Ready with its blocked label rather than occupying review/verification capacity while that correction is blocked. Its completion evidence and clocks are preserved. Resume the remaining documentation criterion after full current-head validation and the feedback-budget correction; do not redo or broaden the already-complete four deletions.
chore: agent-claim #679 nonce=e3bd3d77ad449cbf54f6628167e28dda
chore: agent-claim #679 nonce=8076b4f9a304fe9c05cff2f048bb9e47