AiLounge Tools

Integration, Deployment & Operations · Release Console

Artifact receipt checks, deploy-group mapping, publish/rollback plans and status aggregation for 22 projects. Templates and inventories only this round: not deployed, authorization pending.Local read-only computation (no network, no upload)

22-project status aggregation

Aggregate the 22 PROJECTS.json rows into a status table: domain→group→release placeholders, status capped at implemented/verified, artifact receipt verdict; never staged/live.

Run in browser

Inputs and parameters

Real example

projects=[{"id":"P01","dir":"P01-pdf","siteId":"pdf","group":"C1"}]
→ rows[0]={id:"P01",group:"C1",domain:"https://pdf.ailounge.top",release:"<release>",statusCap:"implemented",note:"未部署/待授权"}

Limits and failure handling

Status capped at implemented/verified; staged/live and "deployment succeeded" claims are forbidden.

FAQ

Why is release a placeholder?

Nothing is deployed; the domain→group→release mapping stays a placeholder until authorization is granted.