docs(plan): step-by-step go-live session walkthrough (You + Claude)#53
Merged
Conversation
Companion to UHHCRAFT-GO-LIVE-PLAN.md: a sequential operator script for running Phase 10 as a live session. Each step is labelled [YOU] / [CLAUDE] / [BOTH] with explicit hand-off cues, so it can be followed top-to-bottom in chat — I run/trigger what I can reach (Semaphore API, OpenBao, Proxmox via the site-config creds, once authorized + reachability confirmed in Step 1), you do the host/dashboard/decision work, and I triage failures. Steps: 0 decisions → 1 reachability handshake → 2 VMs → 3 GPU passthrough → 4 DNS/Stripe → 5 secrets → 6 policies/SSH/podman → 7 ordered deploy (+triage) → 8 smoke → 9 rollback drill → 10 sign-off. Includes a who-owns-what table. Cross-linked from the go-live plan + architecture-reference index.
📝 WalkthroughWalkthroughThis PR introduces a comprehensive go-live walkthrough runbook ( ChangesGo-Live Walkthrough Runbook
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested labels
Poem
Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (9 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
plan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md (1)
10-172:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftThis plan doc is missing required standard sections.
For
plan/**/*.md, this should include the required sections (Problem, Design Principles, Architecture with at least one Mermaid diagram, Implementation Phases with acceptance criteria, Validation Criteria, Security Considerations). Add those sections or explicitly convert this into a non-plan doc location/type if it is intended to be a pure runbook.As per coding guidelines: “include required sections in each plan doc … Architecture w/ at least one Mermaid diagram; Implementation Phases w/ acceptance criteria; Validation Criteria; Security Considerations.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@plan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md` around lines 10 - 172, The walkthrough file "UhhCraft Go-Live — Session Walkthrough (You + Claude)" is missing required plan sections; update this document (or move it out of plan/ if intended as a pure runbook) by adding the top-level headings: Problem, Design Principles, Architecture (include at least one Mermaid diagram), Implementation Phases (break into phases with explicit acceptance criteria for each), Validation Criteria, and Security Considerations; ensure these sections appear before or alongside the existing step-by-step walkthrough (you can reference existing Step 0–Step 10 headings for context) so the doc conforms to the plan/**.md guideline.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@plan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md`:
- Around line 163-171: The Markdown fails lint rules MD022/MD058 because
headings and the revision table lack surrounding blank lines; update the
"Cross-references" and "Revision history" blocks so there is a blank line before
each "## Cross-references" and "## Revision history" heading and ensure a blank
line above and below the revision table (the pipe-delimited table under
"Revision history") so the headings and table have proper spacing for
markdownlint.
- Line 4: The frontmatter uses a non-enum value "status: ACTIVE — ready to run";
change the frontmatter to use the exact enum token by setting status: ACTIVE and
remove the trailing explanatory text from that line, then move the explanatory
phrase ("ready to run") into a separate field (e.g., add context: "ready to
run") or place it into the document body; update the frontmatter block where the
status key is defined to reflect only the enum value and ensure any consumers
read the new context field or body content instead.
---
Outside diff comments:
In `@plan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md`:
- Around line 10-172: The walkthrough file "UhhCraft Go-Live — Session
Walkthrough (You + Claude)" is missing required plan sections; update this
document (or move it out of plan/ if intended as a pure runbook) by adding the
top-level headings: Problem, Design Principles, Architecture (include at least
one Mermaid diagram), Implementation Phases (break into phases with explicit
acceptance criteria for each), Validation Criteria, and Security Considerations;
ensure these sections appear before or alongside the existing step-by-step
walkthrough (you can reference existing Step 0–Step 10 headings for context) so
the doc conforms to the plan/**.md guideline.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: f01b4548-397d-47bd-8421-c21c1a98db4d
📒 Files selected for processing (3)
plan/architecture/architecture-reference.mdplan/development/UHHCRAFT-GO-LIVE-PLAN.mdplan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md
…bbit) - status: ACTIVE (bare enum per architecture-reference.md doc standard) on the go-live walkthrough AND the go-live plan; explanatory text lives in the title/intro, not the status token. - blank lines around the Cross-references/Revision-history headings + table (MD022/MD058) in the walkthrough.
Member
Author
|
Both fixed in 7e8a0a3:
|
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
plan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md (2)
1-8:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd required
contextfield in frontmatter.Frontmatter is missing the required
contextkey for plan docs.Suggested minimal fix
--- title: UhhCraft Go-Live — Session Walkthrough (You + Claude) date: 2026-06-04 status: ACTIVE +context: Live-session execution companion runbook for Phase 10 go-live. audience: the operator (you) running this go-live in a live session with Claude companion_to: UHHCRAFT-GO-LIVE-PLAN.md tags: [uhhcraft, go-live, phase-10, walkthrough, runbook, operator] ---As per coding guidelines: “Frontmatter (Date, Status, Context)” is required for plan docs.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@plan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md` around lines 1 - 8, The frontmatter block is missing the required "context" key; update the document's frontmatter (the YAML block containing title, date, status, audience, companion_to, tags) by adding a top-level "context" field with an appropriate value (e.g., "go-live walkthrough" or "operator session") so the frontmatter contains Date, Status and Context as required by the plan docs guidelines.
1-173:⚠️ Potential issue | 🟠 Major | 🏗️ Heavy liftRequired plan template sections are missing for a
plan/**/*.mddocument.This runbook is operationally strong, but it does not follow the required plan-doc section contract (Problem, Design Principles, Architecture with Mermaid, Implementation Phases, Validation Criteria, Security Considerations). Please either align this file to that template or explicitly reclassify/move it outside the plan-doc template scope.
As per coding guidelines: “plan/frontmatter standards: ensure every plan doc includes … the required sections list (Problem, Design Principles, Architecture w/ mermaid, Implementation Phases, Validation Criteria, Security Considerations, Cross-references, Revision History).”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@plan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md` around lines 1 - 173, The document titled "UhhCraft Go-Live — Session Walkthrough (You + Claude)" is missing the required plan-template sections; either add them or explicitly reclassify the file outside the plan-doc scope. Fix by adding the mandated sections (Problem, Design Principles, Architecture with a Mermaid diagram, Implementation Phases, Validation Criteria, Security Considerations, Cross-references, Revision History) into the body of the markdown (retain the existing step-by-step walkthrough content under Implementation Phases or an Appendix), or move/reclassify the file out of the plan/* directory and update its frontmatter status/tags to reflect "runbook" rather than a plan so it no longer must conform to the plan template; ensure the frontmatter and title "UhhCraft Go-Live — Session Walkthrough (You + Claude)" and companion_to references remain consistent with the chosen option.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@plan/development/UHHCRAFT-GO-LIVE-PLAN.md`:
- Around line 1-7: The frontmatter for the plan (the YAML block containing
title, date, status, audience, tags) is missing the required context field; add
a top-level context: "<short context string>" entry (e.g., context: "production
rollout validation for UhhCraft Phase 10") to the frontmatter so it includes
Date, Status, and Context per the plan doc standard and retains existing fields
(title, date, status, audience, tags).
---
Outside diff comments:
In `@plan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md`:
- Around line 1-8: The frontmatter block is missing the required "context" key;
update the document's frontmatter (the YAML block containing title, date,
status, audience, companion_to, tags) by adding a top-level "context" field with
an appropriate value (e.g., "go-live walkthrough" or "operator session") so the
frontmatter contains Date, Status and Context as required by the plan docs
guidelines.
- Around line 1-173: The document titled "UhhCraft Go-Live — Session Walkthrough
(You + Claude)" is missing the required plan-template sections; either add them
or explicitly reclassify the file outside the plan-doc scope. Fix by adding the
mandated sections (Problem, Design Principles, Architecture with a Mermaid
diagram, Implementation Phases, Validation Criteria, Security Considerations,
Cross-references, Revision History) into the body of the markdown (retain the
existing step-by-step walkthrough content under Implementation Phases or an
Appendix), or move/reclassify the file out of the plan/* directory and update
its frontmatter status/tags to reflect "runbook" rather than a plan so it no
longer must conform to the plan template; ensure the frontmatter and title
"UhhCraft Go-Live — Session Walkthrough (You + Claude)" and companion_to
references remain consistent with the chosen option.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: 0d95899c-9dbc-4d19-9062-6dc2121001e4
📒 Files selected for processing (2)
plan/development/UHHCRAFT-GO-LIVE-PLAN.mdplan/development/UHHCRAFT-GO-LIVE-WALKTHROUGH.md
Comment on lines
1
to
7
| --- | ||
| title: UhhCraft Go-Live — Phase 10 Production Validation Plan | ||
| date: 2026-06-02 | ||
| status: ACTIVE — execution pending hardware + decisions | ||
| status: ACTIVE | ||
| audience: operator running Semaphore against the live cluster, and any agent preparing/triaging the rollout | ||
| tags: [uhhcraft, inference-comfyui, inference-hunyuan3d, caddy, phase-10, go-live, validation, proxmox, openbao] | ||
| --- |
There was a problem hiding this comment.
Frontmatter still misses required context field.
status is now correct, but this plan frontmatter still lacks context, which is required by the plan doc standard.
Suggested minimal fix
---
title: UhhCraft Go-Live — Phase 10 Production Validation Plan
date: 2026-06-02
status: ACTIVE
+context: Phase 10 production go-live checklist/reference for operator execution.
audience: operator running Semaphore against the live cluster, and any agent preparing/triaging the rollout
tags: [uhhcraft, inference-comfyui, inference-hunyuan3d, caddy, phase-10, go-live, validation, proxmox, openbao]
---As per coding guidelines: “Frontmatter (Date, Status, Context)” is required for plan docs.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| --- | |
| title: UhhCraft Go-Live — Phase 10 Production Validation Plan | |
| date: 2026-06-02 | |
| status: ACTIVE — execution pending hardware + decisions | |
| status: ACTIVE | |
| audience: operator running Semaphore against the live cluster, and any agent preparing/triaging the rollout | |
| tags: [uhhcraft, inference-comfyui, inference-hunyuan3d, caddy, phase-10, go-live, validation, proxmox, openbao] | |
| --- | |
| --- | |
| title: UhhCraft Go-Live — Phase 10 Production Validation Plan | |
| date: 2026-06-02 | |
| status: ACTIVE | |
| context: Phase 10 production go-live checklist/reference for operator execution. | |
| audience: operator running Semaphore against the live cluster, and any agent preparing/triaging the rollout | |
| tags: [uhhcraft, inference-comfyui, inference-hunyuan3d, caddy, phase-10, go-live, validation, proxmox, openbao] | |
| --- |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@plan/development/UHHCRAFT-GO-LIVE-PLAN.md` around lines 1 - 7, The
frontmatter for the plan (the YAML block containing title, date, status,
audience, tags) is missing the required context field; add a top-level context:
"<short context string>" entry (e.g., context: "production rollout validation
for UhhCraft Phase 10") to the frontmatter so it includes Date, Status, and
Context per the plan doc standard and retains existing fields (title, date,
status, audience, tags).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A sequential operator script for running the UhhCraft go-live as a live session — the how-we-execute-together companion to the comprehensive
UHHCRAFT-GO-LIVE-PLAN.md(the what).Each step is labelled [YOU] / [CLAUDE] / [BOTH] with an explicit hand-off cue (the exact thing to say/paste to move on), so you can follow it top-to-bottom in chat.
The flow
Key design points
Cross-linked from the go-live plan +
architecture-reference.md. Docs only; links resolve,plan/ASCII-art gate + secret/IP audit clean.AI Layer
Guardrail Layer
Automation Layer
Platform Layer
Architectural scope & decisions (summary)
(Notes) This PR is documentation-only; it updates plan frontmatter to status: ACTIVE and adds the walkthrough runbook and index entry. No secrets, policies, code, or manifests were changed by these commits.