docs: site-config handling memory + phase-progress refresh

[JacobHaig]

Memory/docs only.

• reference-site-config-repo memory — records the user's rules for the private uhstray-io/site-config repo: never copy its contents into public repos/commits/PRs/memory (placeholders only), additive WisBot-only edits, work isolated off main, OpenBao is the runtime source of truth. Contains no actual values from site-config.
• Refreshes the deployment-progress memory (file relay 8a/8b merged; Phase 7 + 8c pending the VM IP/VMID/node, tracked in site-config NEXT-STEPS) + indexes the new memory.

[claude]

⚠️ Code review skipped — your organization's overage spend limit has been reached.

Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit at claude.ai/admin-settings/claude-code.

Once credits are available, reopen this pull request to trigger a review.

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated deployment progress tracking with latest milestone completions and remaining operational steps.
  • Added reference guidelines for best practices in configuration repository management.

Walkthrough

This PR updates memory and documentation files to track WisBot deployment progress and establish private site-config handling guidelines. It documents Milestone D completion (file relay service), enumerates remaining operational deployment phases, and introduces strict rules for working with the isolated private infrastructure repository.

Changes

Deployment Progress and Site-Config Handling

Layer / File(s)	Summary
Deployment progress tracking and operational phases .claude/memory/MEMORY.md, .claude/memory/project-deployment-phase-progress.md	Updated Memory Index to reflect Milestone D completion (/upload file relay service merged) and remaining Phase 7/8c operational requirements (site-config edits, secrets seeding, VM provisioning, deployment). Recorded locked decisions for secret/services/wisbot, wisbot.uhstray.io subdomain, and wisbot_guild_id source. Clarified workflow using isolated worktrees with additive-only private site-config handling.
Private site-config repository handling guide .claude/memory/reference-site-config-repo.md	New reference documentation for the private uhstray-io/site-config repository establishing strict rules: prevent credential/IP leakage, restrict edits to WisBot-specific additive changes, require isolated feature branches, and minimize sensitive value exposure. Points to site-config's own tracking for pending WisBot infrastructure changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• uhstray-io/WisBot#13: Both PRs modify deployment-phase memory files (.claude/memory/MEMORY.md and .claude/memory/project-deployment-phase-progress.md) to track Milestone/Phase progress and file relay service details.
• uhstray-io/WisBot#8: Both PRs update MEMORY.md to refine Memory Index guidance; this PR adds site-config and deployment guidance while the prior PR establishes broader behavioral rules for the memory index mechanism.
• uhstray-io/WisBot#9: This PR's deployment-phase and site-config guidance builds directly on the agent-cloud deployment memory introduced in PR #9, continuing the migration documentation.

Poem

🐰 A tale of migration, carefully told,
Milestones tracked, and site-config held,
In memory files, deployment paths gleam,
With secrets secure, a coordinated scheme! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main changes: adding site-config handling memory documentation and refreshing the phase-progress memory.
Description check	✅ Passed	The description is directly related to the changeset, explaining the memory documentation additions and deployment progress updates with appropriate context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/site-config-memory

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

.claude/memory/reference-site-config-repo.md (1)

1-7: 💤 Low value

Consider reviewing the metadata type field.

The frontmatter specifies type: feedback, but this document appears to be a reference guide establishing handling rules for the private site-config repository. Based on naming patterns in MEMORY.md, documents prefixed with reference- might be better categorized as type: reference or type: project rather than type: feedback.

Verify whether feedback accurately describes this memory node's purpose in your taxonomy.

🤖 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 @.claude/memory/reference-site-config-repo.md around lines 1 - 7, The
frontmatter for the memory node named "reference-site-config-repo" incorrectly
uses type: feedback; update the metadata `type` to the correct category (e.g.,
`reference` or `project`) that matches its purpose, and confirm consistency with
MEMORY.md naming conventions; specifically change the `type` field in the
frontmatter for the node named reference-site-config-repo, run a quick scan for
other `reference-` prefixed entries to ensure they use the same `type`, and
update documentation or tests that validate node taxonomy if needed.

🤖 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.

Nitpick comments:
In @.claude/memory/reference-site-config-repo.md:
- Around line 1-7: The frontmatter for the memory node named
"reference-site-config-repo" incorrectly uses type: feedback; update the
metadata `type` to the correct category (e.g., `reference` or `project`) that
matches its purpose, and confirm consistency with MEMORY.md naming conventions;
specifically change the `type` field in the frontmatter for the node named
reference-site-config-repo, run a quick scan for other `reference-` prefixed
entries to ensure they use the same `type`, and update documentation or tests
that validate node taxonomy if needed.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 676b0aba-a348-4b8a-854b-a345cc1c1970

📥 Commits

Reviewing files that changed from the base of the PR and between 61ed442 and 7e43b26.

📒 Files selected for processing (3)

• .claude/memory/MEMORY.md
• .claude/memory/project-deployment-phase-progress.md
• .claude/memory/reference-site-config-repo.md

📜 Review details

🧰 Additional context used

🪛 LanguageTool

.claude/memory/project-deployment-phase-progress.md

[style] ~25-~25: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... download); gated on UploadEnabled. - Phase 8b (#17) — hourly retention loop delete...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[grammar] ~32-~32: Use a hyphen to join words.
Context: ...isolated worktree off main + stage specific files (never git add -A). For...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (9)

.claude/memory/MEMORY.md (1)

6-7: LGTM!

.claude/memory/project-deployment-phase-progress.md (4)

21-25: LGTM!

---

27-28: LGTM!

---

30-30: LGTM!

---

32-32: LGTM!

.claude/memory/reference-site-config-repo.md (4)

9-9: LGTM!

---

11-15: LGTM!

---

17-17: LGTM!

---

19-19: LGTM!