docs: record v0.1.0 publication

README.md

@@ -265,8 +265,8 @@ log-availability, and rendered manifest evidence before repair. A two-step
 Git-revert test reproduced and then recovered that failure through Argo CD.
 The final state is `Synced` and `Healthy`; the Deployment is Available, its pod
 is Ready, the HPA has CPU metrics, and all endpoints return the expected
-`v0.1.3` responses. Release `v0.1.0` is prepared; creating and pushing its Git
-tag requires explicit approval.
+`v0.1.3` responses. Project 5 release `v0.1.0` is published as an annotated Git
+tag on validated commit `cdf7303`.
 
 Published image:
 

docs/issues/008-failure-rollback-and-release.md

@@ -45,5 +45,6 @@ first complete Project 5 release.
 - Repository secret-pattern checks passed, and no Secret value, token,
   kubeconfig, or credential was committed.
 
-All acceptance criteria are met. Release `v0.1.0` is prepared, but its tag must
-not be created or pushed until explicit approval is given.
+All acceptance criteria are met. After explicit approval, annotated tag
+`v0.1.0` was created on validated release commit `cdf7303` and pushed to
+`origin`.

docs/project-journal.md

@@ -7,8 +7,8 @@ it factual and replace stale status rather than accumulating a transcript.
 
 - **Project:** 5 — Kubernetes Deployment and GitOps Workflow
 - **State:** Issues 001–008 and the Project 5 completion gate are complete;
-  `v0.1.0` release metadata is prepared but no tag exists yet
-- **Branch:** `feature/008-prepare-v0.1.0-release`
+  annotated release tag `v0.1.0` is published
+- **Branch:** `feature/008-record-v0.1.0-release`
 - **Remote:** `origin` points to the public GitHub Project 5 repository
 - **Target:** Docker Desktop local Kubernetes; context `docker-desktop` is
   active and its control-plane node is Ready
@@ -114,6 +114,10 @@ it factual and replace stale status rather than accumulating a transcript.
   HPA reported a valid CPU metric.
 - Reviewed every Project 5 completion-gate criterion and recorded its evidence
   in Issue 008. Prepared the `v0.1.0` changelog entry without creating a tag.
+- Merged the release metadata through pull request 19 at validated commit
+  `cdf7303`. After explicit approval, created annotated tag `v0.1.0` on that
+  commit and pushed only that tag to `origin`; remote verification resolved
+  the annotated tag to `cdf7303`.
 
 ## Decisions
 
@@ -127,9 +131,8 @@ it factual and replace stale status rather than accumulating a transcript.
 
 ## Resume here
 
-Review and merge the `v0.1.0` release metadata after its pull-request checks
-pass. Pull `main`, verify the release commit, and request explicit approval
-before creating or pushing the `v0.1.0` tag.
+Review and merge this post-release status update. Project 5 is then complete;
+begin another project only after the learner agrees to proceed.
 
 ## Open questions