Compare commits

...
2 Commits
Author SHA1 Message Date
tony 8507a3c6b6 Merge pull request 'fix(rc): resolve pre-release blockers' (#52) from codex/block-24-pre-rc-audit into main
CI / validate (push) Successful in 26m33s
Reviewed-on: #52
2026-08-27 00:40:31 +02:00
codex a665585dbe fix(rc): resolve pre-release blockers
CI / validate (pull_request) Successful in 26m32s
2026-08-27 00:17:46 +02:00
2 changed files with 23 additions and 0 deletions
+1
View File
@@ -90,6 +90,7 @@ Read this compact operational baseline before starting a milestone. Open detaile
## Known limitations and debt
- The Block 24 pre-release audit (2026-08-27) found and fixed a deployment-page artwork overflow at desktop widths. The fresh Palworld lifecycle run could not proceed because the declared registry `:latest` image was unavailable in the audit environment; a local versioned image retag did not make the agent installation succeed, so no Palworld runtime data was altered. The direct Didstopia V Rising image reached SteamCMD but failed before server startup with its external `beta '='`/missing configuration error; this remains an external image/SteamCMD limitation, not a DoGaMa defect.
- Scheduled backup outcomes and repeated authentication blocks are audited/logged, but broader scheduler-origin notification coverage remains intentionally limited to events emitted by implemented workflows.
- The Dashboard links to an SSR instance detail page through opaque registry IDs. It uses existing lifecycle and backup services for CSRF-protected actions and a validated sandboxed WASM facade for declared live server info, metrics, player lists, banned-player lists and permitted player/announcement actions. Unban uses a fresh adapter `list_bans` result when available; otherwise, it accepts a bounded manual game identifier for the module to validate. Update availability is limited to immutable candidates explicitly approved in a template; games without one remain safely unknown and no registry browsing is performed.
- Template configuration targets are applied during deployment: container environment and argv are included in the signed agent plan; INI changes are applied atomically after an optional restore and before start. Instance secrets are encrypted outside preview JSON.
+22
View File
@@ -1055,6 +1055,28 @@ button:disabled{
align-items: center;
gap: 12px
}
.deployment-layout{
display: grid;
grid-template-columns: minmax(220px,.8fr) minmax(0,1.2fr);
gap: 22px;
max-width: 1120px;
margin: auto
}
.deployment-game img{
display: block;
width: 100%;
max-height: 320px;
object-fit: cover;
border-radius: 10px
}
.deployment-form{
min-width: 0
}
@media(max-width:700px){
.deployment-layout{
grid-template-columns: 1fr
}
}
.scan-button,.deploy-band button{
border: 1px solid #20d9f388;
border-radius: 10px;