browser/openspec/changes/refresh-architecture-delivery-stream/tasks.md

1. Refresh Current Queue State

• 1.1 Update openspec/changes/architecture-delivery-stream/delivery-plan.md so completed changes from openspec list are marked complete and no completed change remains active.
• 1.2 Record fix-env-profile-settings as the current guard until its browser walkthrough task is closed or explicitly blocked with evidence.
• 1.3 Replace the stale pending tail with the proof-oriented backlog from this design.

2. Add Next-Change Pointer

• 2.1 Create openspec/changes/architecture-delivery-stream/NEXT_CHANGE.md with the current guard, next change name, creation prompt, implementation prompt, and stop condition.
• 2.2 Add a generator prompt that creates exactly one new OpenSpec and stops after strict validation.
• 2.3 Add an implementation prompt that implements exactly one OpenSpec and updates the queue before closing.

3. Seed The Next Concrete OpenSpec Prompt

• 3.1 Record verify-current-platform-e2e-baseline as the first concrete OpenSpec to generate after the active guard is closed or explicitly reprioritized.
• 3.2 Ensure the generation prompt requires browser walkthrough, platform APIs, run-mediated server lifecycle, durable log history, artifact transfer, plugin marketplace, user management, and AI provider settings coverage.
• 3.3 Record that the next generator chat must validate verify-current-platform-e2e-baseline and update NEXT_CHANGE.md to point at implementing it.

4. Verification

• 4.1 Run openspec validate refresh-architecture-delivery-stream --strict.
• 4.2 Run scripts/check-structure.sh.
• 4.3 Record verification evidence in this task file before marking this change complete.

Verification Evidence

• 2026-07-08: openspec validate refresh-architecture-delivery-stream --strict passed. OpenSpec telemetry flush reported restricted DNS for edge.openspec.dev; the command still exited 0 and the change was valid.
• 2026-07-08: scripts/check-structure.sh passed with structure check passed.