Homelab/infra-core
6
0
Fork 2
Code Issues Pull requests 35 Projects Releases 1 Packages Wiki Activity Actions

HOMELAB-2682: chore(tooling): relief threshold 55->30 (one setting, RELIEF_THRESHOLD, default 30) #878

Closed
pi-landing wants to merge 1 commit from plane/HOMELAB-2682-relief-threshold into live
pull from: plane/HOMELAB-2682-relief-threshold
merge into: Homelab:live
Conversation 1 Commits 1 Files changed 7 +28 -14
pi-landing commented 2026-11-06 19:35:25 +00:00
Collaborator
Copy link

One setting, RELIEF_THRESHOLD, default 30, in every copy of the relief threshold. The 55 (and its per-file constant) is gone.

Ruling 5 (El Director's threshold order). Nothing else changes: every other byte is identical.

file what changed
sbx-common-phase1/epic-supervisor.wait-orchestrator.sh RELIEF_THRESHOLD="${RELIEF_THRESHOLD:-30}" at the top; the comparison and the usage line use it; 55 removed
sbx-common-phase1/epic-supervisor.SKILL.md §6 and the CONTEXTO reading say RELIEF_THRESHOLD (30 % by default)
sbx-common/supervisor-epica.espera-orq.sh same setting, same name, same default 30 (es)
sbx-common/supervisor-epica.SKILL.md same wording (es)
sbx-gits/reglas-fijas.md new short section naming the setting, so every session of the pod reads it
both SHA256SUMS regenerated in place; only the four changed files move, so the seed's hash check stays true

Why sbx-common too: the Spanish copies in sbx-common are the relief path that sbx-sendrast still runs. The order is across every copy, and the threshold is one number; leaving 55 there would re-introduce the split. The phase-1 guard (no renames/deletes in sbx-common) is untouched — no file was added, renamed or removed there beyond the content edit.

Verify: bash -n and shellcheck on both scripts (only pre-existing SC2034/SC1010 warnings on untouched lines), grep 55 clean in both components, sha256sum -c clean against both regenerated SHA256SUMS.

The mgmt-VM copies (~/.claude/skills/{epic-supervisor,overseer}, ~/.pi/agent/extensions/skills/{overseer,supervisor-epica}, working-files/gits/orch-watch.py) carry the same setting and are edited in place — they are not in this repo.

Nothing is restarted or reloaded: the pods pick the new skills up on their next start via seed-pi-agent.

One setting, `RELIEF_THRESHOLD`, default **30**, in every copy of the relief threshold. The 55 (and its per-file constant) is gone. Ruling 5 (El Director's threshold order). Nothing else changes: every other byte is identical. | file | what changed | |---|---| | `sbx-common-phase1/epic-supervisor.wait-orchestrator.sh` | `RELIEF_THRESHOLD="${RELIEF_THRESHOLD:-30}"` at the top; the comparison and the usage line use it; `55` removed | | `sbx-common-phase1/epic-supervisor.SKILL.md` | §6 and the CONTEXTO reading say `RELIEF_THRESHOLD` (30 % by default) | | `sbx-common/supervisor-epica.espera-orq.sh` | same setting, same name, same default 30 (es) | | `sbx-common/supervisor-epica.SKILL.md` | same wording (es) | | `sbx-gits/reglas-fijas.md` | new short section naming the setting, so every session of the pod reads it | | both `SHA256SUMS` | regenerated in place; only the four changed files move, so the seed's hash check stays true | **Why `sbx-common` too:** the Spanish copies in `sbx-common` are the relief path that `sbx-sendrast` still runs. The order is *across every copy*, and the threshold is one number; leaving 55 there would re-introduce the split. The phase-1 guard (no renames/deletes in `sbx-common`) is untouched — no file was added, renamed or removed there beyond the content edit. **Verify:** `bash -n` and `shellcheck` on both scripts (only pre-existing SC2034/SC1010 warnings on untouched lines), `grep 55` clean in both components, `sha256sum -c` clean against both regenerated `SHA256SUMS`. The mgmt-VM copies (`~/.claude/skills/{epic-supervisor,overseer}`, `~/.pi/agent/extensions/skills/{overseer,supervisor-epica}`, `working-files/gits/orch-watch.py`) carry the same setting and are edited in place — they are not in this repo. Nothing is restarted or reloaded: the pods pick the new skills up on their next start via `seed-pi-agent`.
HOMELAB-2682: chore(tooling): relief threshold 55->30
All checks were successful
CI Review / runner-manifest-test (pull_request) Successful in 7s
Details
CI Review / helm-validate (pull_request) Successful in 12s
Details
CI Review / receiver-test (pull_request) Successful in 7s
Details
Lint & Validate / shellcheck (pull_request) Successful in 8s
Details
CI Review / alert-receiver-test (pull_request) Successful in 23s
Details
Lint & Validate / yaml-lint (pull_request) Successful in 24s
Details
CI Review / record-sql-test (pull_request) Successful in 56s
Details
Lint & Validate / terraform-validate (pull_request) Successful in 1m56s
Details
CI Review / cockpit-test (pull_request) Successful in 2m32s
Details
CI Review / dispatcher-test (pull_request) Successful in 2m41s
Details
CI Review / cockpit-e2e (pull_request) Successful in 2m42s
Details
80cd9eb598 
One setting, RELIEF_THRESHOLD, default 30, in every copy of the relief
threshold. The 55 (and its per-file constant) is gone.

- sbx-common-phase1/epic-supervisor.wait-orchestrator.sh: RELIEF_THRESHOLD=30
- sbx-common-phase1/epic-supervisor.SKILL.md: SS6 says RELIEF_THRESHOLD (30 % by default)
- sbx-common/supervisor-epica.espera-orq.sh: same setting, same default
- sbx-common/supervisor-epica.SKILL.md: same wording (es)
- sbx-gits/reglas-fijas.md: the setting named for every session of the pod
- both SHA256SUMS regenerated (only the four changed files move)

Nothing else changes: byte-identical elsewhere.
pi-landing commented 2026-11-06 20:56:08 +00:00
Author
Collaborator
Copy link

Superseded by #880 (phase1-only split per El Director's ruling). Sendrast render proven byte-identical; Sendrast stays at 55.

Superseded by #880 (phase1-only split per El Director's ruling). Sendrast render proven byte-identical; Sendrast stays at 55.
pi-landing closed this pull request 2026-11-06 20:56:10 +00:00
All checks were successful
CI Review / runner-manifest-test (pull_request) Successful in 7s
Details
CI Review / helm-validate (pull_request) Successful in 12s
Required
Details
CI Review / receiver-test (pull_request) Successful in 7s
Details
Lint & Validate / shellcheck (pull_request) Successful in 8s
Required
Details
CI Review / alert-receiver-test (pull_request) Successful in 23s
Details
Lint & Validate / yaml-lint (pull_request) Successful in 24s
Required
Details
CI Review / record-sql-test (pull_request) Successful in 56s
Details
Lint & Validate / terraform-validate (pull_request) Successful in 1m56s
Required
Details
CI Review / cockpit-test (pull_request) Successful in 2m32s
Details
CI Review / dispatcher-test (pull_request) Successful in 2m41s
Details
CI Review / cockpit-e2e (pull_request) Successful in 2m42s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
operator-review

Requires human operator review before merge — dangerous class (RBAC, secrets, network policy, Terraform) or explicitly gated. Never auto-merge.

No labels
operator-review
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Homelab/infra-core!878
No description provided.