no-planned-replace
Keep slice limit changes from becoming disruptive restarts. Use when changing systemd limits, reviewing replacement plans, or modifying unit reconciliation. The enforced scope is active slice updates, not a global plan veto.
Datos de origen
- Repositorio
- joelhooks/alchemy-celld
- Última actividad en el origen
- 17 de octubre de 2026 a las 18:06
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 56
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- no-planned-replace
- description
- Keep slice limit changes from becoming disruptive restarts. Use when changing systemd limits, reviewing replacement plans, or modifying unit reconciliation. The enforced scope is active slice updates, not a global plan veto.
# No planned replace: the slice case
This is a specific case of [uncomplect](../uncomplect/SKILL.md): separate a configuration change from replacing running work.
**Enforced:** `src/systemd.ts` writes changed active slice declarations and daemon-reloads them without issuing restart. Changed non-slice units still restart when required, after a bounded activation wait. Explicit `started: false` still stops a slice.
On 2026-10-17, a generic unit reconcile restarted a slice after its memory cap changed. That restarted every service in the slice. Reloading the declaration applies the limit without replacing those service invocations.
**Not enforced globally:** identity changes still produce replacement plans in file, directory, binary, unit, node, bucket, and deployment providers. `AGENTS.md` lists the source locations. Stop on a planned replacement; this skill is not permission to apply one.
Check `test/unit-restart-safety.test.ts` and the gated `test/systemd-live.test.ts`. The real test requires unchanged member InvocationID and MainPID plus the new MemoryMax. See [the live procedure](../test-against-the-real-thing/SKILL.md). A successful daemon-reload alone is not proof that a member survived.
Ver en GitHub