docs(ops): move hosted deployment details private - #470
Merged
Merged
Conversation
JayZeeDesign
added a commit
that referenced
this pull request
Sep 13, 2026
…rivate Resolves the conflicts from #470: render.yaml is gone (the Harvest key slot and capacity-cron forwarding now belong to the private deployment repository), the Harvest sections of ops/deploy.md and ops/capacity.md follow the hosted details out of this repo, and the harvestapi fragment records the hosted wiring in one paragraph instead. Context map and the three skill mirrors regenerated. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015vSvXHoJ2rrEpgoH7kdrsh
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
Private dependency
Merge superdesigndev/treg-internal#28 first so the operator links resolve before this public change lands.
Validation
Deployment impact
No production configuration was changed and no deployment was triggered. The deleted root render.yaml was not the production source of truth; treg-internal owns the current non-secret production configuration.