From 43e89732fd89ea93e70be50ce6dcabfc84a4c384 Mon Sep 17 00:00:00 2001 From: Sam Catlow Date: Sun, 11 Oct 2026 14:43:36 +1100 Subject: [PATCH] docs(wiki): focus guide on current setup --- Home.md | 20 ++++---------------- Migration-to-Gitea.md | 8 ++++---- 2 files changed, 8 insertions(+), 20 deletions(-) diff --git a/Home.md b/Home.md index 2f4c20b..a4e19df 100644 --- a/Home.md +++ b/Home.md @@ -1,6 +1,6 @@ # Archie development and release guide -This guide is the working plan for moving Archie into private development on Gitea and establishing reliable releases. It records the decisions made on 11 October 2026. The procedures described as planned still need implementation; they are not claims that the pipeline exists today. +This guide is the working plan for moving Archie into private development on Gitea and establishing reliable releases. The procedures described as planned still need implementation; they are not claims that the pipeline exists today. The objective is a repeatable path from a selected commit to a verified installation. Computers build, install, test, collect evidence, and recover. Sam decides product scope, accepts known limitations, and approves deployment to production. @@ -21,8 +21,6 @@ The migration and tracking setup can progress together. A stable release depends | Decision | Direction | |---|---| | Development forge | Private `sam/archie` on Gitea | -| Git object format | SHA-1, retaining original commit IDs and signatures | -| Historical reference | Original SHA-1 history retained separately | | Release numbering | New `0.x` series, beginning with `0.1.0` | | Product maturity | `1.0.0` will represent a defined supported product | | Project management | Move from Beads to Gitea issues, milestones, and a project board | @@ -31,24 +29,14 @@ The migration and tracking setup can progress together. A stable release depends Future licensing and commercial terms remain a separate decision. Repository privacy does not revoke the Apache 2.0 rights attached to previously published versions. -## Verified migration results +## Current setup -The recreated Gitea repository is private and uses SHA-1. The original history was restored from `/work/apps/archie-core`, retaining all 2,362 commits reachable from its 19 local branches, their original IDs, and existing commit signatures. Historical release tags are excluded from the new repository so the new `0.x` release series can start independently. - -The earlier SHA-256 conversion was reversed by restoring the original repository, rather than converting the rewritten objects back. No new commits were found on the converted local branches. The original `main` at restoration was `3066c3b02f306ed794924dbc60145a4d0eb7f1c2`; this is a historical checkpoint, not a promise about future branch tips. - -The guide was preserved locally when the repository and wiki were recreated. The active wiki clone is SHA-1 too. The SHA-256 clones remain as local archives and should not receive new development work. - -Local locations: +Development is hosted in the private Gitea repository `sam/archie`, with `main` as the default branch. Commit history and branches are preserved. Historical release tags are excluded so the new `0.x` release series can start independently. - Development checkout: `/work/apps/archie-sha1`, with `origin` pointing to Gitea. -- Original checkout: `/work/apps/archie-core`. - Wiki checkout: `/work/apps/archie.wiki`. -- Archived SHA-256 code checkout: `/work/apps/archie-sha256`. -- Archived SHA-256 wiki checkout: `/work/apps/archie.wiki-sha256`. -- Original refs bundle and conversion evidence: `/work/apps/archie-sha256/.git/migration`. -Runner workflows, private distribution, project tracking, staging QA, and release automation still require implementation. The repository-format reversal does not change that plan. +Runner workflows, private distribution, project tracking, staging QA, and release automation still require implementation. ## How to maintain this guide diff --git a/Migration-to-Gitea.md b/Migration-to-Gitea.md index 3ca682b..7337137 100644 --- a/Migration-to-Gitea.md +++ b/Migration-to-Gitea.md @@ -2,19 +2,19 @@ [Guide home](Home) ยท [Next: project tracking](Project-Tracking) -The original SHA-1 history has been restored and pushed. The remaining migration is the development workflow, distribution, and tooling around the repository. +The code and history are available in `sam/archie`. The remaining migration is the development workflow, distribution, and tooling around the repository. ## 1. Establish the development home -Use `sam/archie` and `/work/apps/archie-sha1` for new work. The checkout's `origin` already points to Gitea. `/work/apps/archie` contained existing files and was not overwritten. +Use `sam/archie` and `/work/apps/archie-sha1` for new work. The checkout's `origin` already points to Gitea. -Retain the original checkout and backup. Copy the original refs bundle to independent backup storage; `.git/migration` in the archived SHA-256 checkout is local evidence and is not included in an ordinary clone. Review the 19 preserved branches and retain the ones that still contain intended work. Decide branch cleanup explicitly after that review. +Keep an independent repository backup. Review the preserved branches and retain the ones that still contain intended work. Decide branch cleanup explicitly after that review. Treat the old GitHub and Gitea repositories as historical references. Disable superseded automatic publishing and unintended mirroring. Verify their visibility separately before treating them as private archives. Confirm repository and backup restoration works before deleting any historical data. A repository rename does not require an immediate rename of Go import paths or service binaries. Keep those changes separate unless a consumer actually requires them. -**Complete when:** a fresh SHA-1 clone is the routine development checkout, active branches are understood, backups are independently recoverable, and superseded publication is disabled. +**Complete when:** a fresh clone is the routine development checkout, active branches are understood, backups are independently recoverable, and superseded publication is disabled. ## 2. Reconnect runners and establish one quality gate