admin343/browser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
ff34a20906e0b2bd5a725f6029c75396b27db01b
browser/openspec/changes/make-run-autonomous-lifecycle-owner/tasks.md
T

2.3 KiB
Raw Blame History

Prompt Boundaries

  • 0.1 正向提示词: Make generated Run packages self-bootstrap from plugin-declared lifecycle plans so the first-party server management area projects state from Run-owned facts.
  • 0.2 方向提示词: Update platform/ build input, registration handling, tests, and protocol docs while preserving existing domain/service/DTO separation; verify with Go tests, OpenSpec validation, and scripts/check-structure.sh.
  • 0.3 任务边界: Do not add a run/ source tree, hardcode SCUM behavior in Platform, expose component keys to machine endpoints, add cloud/billing/provider workflows, or touch unrelated frontend styling.

1. OpenSpec Contract

  • 1.1 Add design and delta specs for Run-owned autonomous lifecycle startup.
  • 1.2 Validate the OpenSpec change strictly before completion.

2. Platform Implementation

  • 2.1 Add autonomous lifecycle plan domain/build-input structures without exposing the plan through machine job-channel DTOs.
  • 2.2 Populate the plan from plugin lifecycle declarations, runtime profile data, dependency declarations, log sources, DLL extensions, and deployment definition.
  • 2.3 Stop generated Run registration from enqueueing bootstrap start or status reconciliation jobs.
  • 2.4 Add a signed Platform lifecycle report endpoint that projects server state from Run-owned terminal lifecycle facts without creating jobs.
  • 2.5 Update protocol and governance docs to make Run the lifecycle authority.

3. Independent Run Implementation

  • 3.1 Add generic autonomous lifecycle plan protocol types and validation in the independent run repository.
  • 3.2 Load .platform/autonomous-lifecycle-plan.json from the generated package workspace, validate package identity/target, run dependency probes/install plans, execute the bootstrap action, and report the terminal lifecycle result to Platform.
  • 3.3 Keep Run generic: no SCUM executable names, Steam app IDs, install paths, ports, or game-specific branches.

4. Verification

  • 4.1 Update service/API/runtime tests for autonomous build input, no registration-time lifecycle dispatch, Run-owned bootstrap execution, lifecycle reporting, and signed report routing.
  • 4.2 Run full Go tests for platform/ and the independent run repository plus repository structure checks.
Reference in New Issue View Git Blame Copy Permalink