Skip to content

Releases

Video Game Technical Director 6.15.8

Choose a tag to compare

@github-actions github-actions released this 20 Nov 15:36

6.15.8

Victor selects the technical constraints that govern each task when refining a Story and binds the stack decision to the runnable setup task. Retained Story indexes carry those selections into later planning.

For PR review, the provider's response schema now requires one judgment per ticket acceptance criterion and one resolution per existing finding. Victor checks applicable implementation constraints, candidate defects, and required validation receipts. Project goals do not add grading rows to an existing ticket.

Video Game Technical Director 6.15.7

Choose a tag to compare

@github-actions github-actions released this 20 Nov 01:03

6.15.7

Adaptive Story planning splits independently verifiable deliverables and records only the prerequisite results each task consumes.

Video Game Technical Director 6.15.6

Choose a tag to compare

@github-actions github-actions released this 19 Nov 04:30

6.15.6

The first setup ticket uses the engine, language and applicable lockfile Victor chose. Victor scopes implementation and verification to the approved Story and applies Gabriel's corrections directly to the draft. In Prism Breaker, setup notes had added deferred audio and visual effects back to the baseline ticket after Gabriel requested their removal.

The C-Sweet AgentTestHost regression replays both a fresh plan and Gabriel returning a conflicting draft to Victor. Each case follows Adrian’s first sprint claim and redelivery after restart.

Video Game Technical Director 6.15.5

Choose a tag to compare

@github-actions github-actions released this 18 Nov 23:49

6.15.5

Victor uses SDK 5.43.1 for file-scoped technical review. Rework reuses unchanged source observations against the same target and planning scope. Victor checks current validation evidence and every acceptance criterion before returning a decision. Exact redelivery revalidates the publication and reuses its recorded verdict. The standalone AgentTestHost suite includes a model-quality check for the audio-readiness incident.

Video Game Technical Director 6.15.4

Choose a tag to compare

@github-actions github-actions released this 18 Nov 20:10

6.15.4

Victor routes the selected engineer's runnable project setup through Code delivery even when a planning reply labels it as a research spike or creative review. The original Story criteria, dependencies, engineer and stack decision carry through. Other research and review tasks keep their own routing.

Video Game Technical Director 6.15.3

Choose a tag to compare

@github-actions github-actions released this 18 Nov 18:48

6.15.3

Victor records the project's stack decision when he freezes a new roadmap. Gabriel can verify the roadmap digest and admit the first engineering Story. Story refinement retains the selected setup and any required lockfile when an older outline predates the stack decision.

Video Game Technical Director 6.15.2

Choose a tag to compare

@github-actions github-actions released this 18 Nov 17:09

6.15.2

The first engineering ticket verifies that the slice launches from a clean checkout. Victor records only the setup steps the chosen stack needs, including when a static project can run directly.

Video Game Technical Director 6.15.1

Choose a tag to compare

@github-actions github-actions released this 18 Nov 17:00

6.15.1

Victor owns engine selection throughout sprint planning. He can revise a technical choice within the approved game scope and coordinates the resulting ticket changes with Gabriel. A change to an explicit business constraint, budget or creative scope goes to its owner.

Video Game Technical Director 6.15.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 16:42

6.15.0

Victor chooses an engine, language and libraries for the accepted game. He records why the stack fits its mechanics and complexity, assesses compatible build recipes, and hands Gabriel one engineer-owned Sprint 1 setup deliverable. The selected package workflow determines whether a lockfile belongs in that task.

Video Game Technical Director 6.14.2

Choose a tag to compare

@github-actions github-actions released this 18 Nov 04:54

6.14.2

Brickfall’s proposed Story refinement already included an engineering task titled “Commit exact Phaser 3 dependency pin for Chromium validation.” Its acceptance criteria required the exact candidate and restored lockfile. Victor now recognizes this explicit dependency owner and preserves the task’s criteria and dependencies. The regression also checks that a separate task which only verifies a pin is treated as a consumer.