Video Game Designer 3.0.0

3.0.0

• Use the single scope-aware work.execution.run contract from SDK and WorkManagement.Contracts 4.0.0.
• Remove the parallel execution capability and task-payload compatibility adapter; retain task, aggregate-review and independent-QA authority checks.
• Breaking coordinated development release: upgrade the platform, SDK and executing agents together. Previously queued legacy execution envelopes must be recreated through normal recovery.

Video Game Designer 2.5.1

2.5.1

Use the shared artifact-delivery contract for exact document handoffs. SDK 3.65.1 reads existing persisted PascalCase outcomes and canonical camelCase outcomes consistently before independent QA. Pin WorkManagement.Contracts 3.29.0.

Video Game Designer 2.5.0

2.5.0

Adopts SDK 3.65.0 shared delegation and outcome tracking. Accepted requests use existing role workflows and canonical work, while coordinators retain durable reporting commitments. Progress notifications are informational and do not widen execution or approval authority.

Video Game Designer 2.4.1

2.4.1

Set the default model context window to 256,000 tokens and maximum output to 128,000 tokens in installation configuration and runtime fallbacks. Explicit installation token settings remain supported.

Video Game Designer 2.4.0

2.4.0

Updates this repository’s own VideoGameAgentKit adapter for V2 assignments, exact artifact revisions and independent QA rework. Preserves its discipline-specific production and approval behavior.

Supports work.execution.run.v2 with explicit Task, Story, Epic or Release scope, assigned principal, planning/scope revisions and exact evidence. Preserves published V1 execution. Uses Agent.SDK 3.59.0 and WorkManagement.Contracts 3.25.0.

Task completion follows independent QA; task/story completion does not promote directly to the default branch. Manager acceptance and trusted release promotion remain separate from deployment or public release.

Video Game Designer 2.3.2

2.3.2

Model-aligned token budgets

• Remove fixed agent-level maximums from the configurable context-window and output-token budgets so users can match the selected model and provider.
• Preserve minimum budgets and existing output-below-context validation where declared; the provider profile remains the authoritative execution ceiling.

Video Game Designer 2.3.1

2.3.1

Expose the model token budgets as installation configuration. maxContextWindowTokens documents the selected model's planning ceiling and maxOutputTokens caps each Game Designer model response. Both settings are required and validated so the output budget stays below the context window. Also fix the stale implementation identity left behind by the 2.3.0 version bump.