Video Game Director 0.5.0

0.5.0

Route supported missing Node/Phaser/Babylon capacity to the current Technical Director as a durable resource requirement instead of an inert manual setup decision. Discover current requests and resume the exact production commitment only after an authorized current read confirms verified readiness.

Support escalated resource plan review through SDK 5.13.0, with resource read/decision grants and change notifications. Existing project feasibility and certified toolchain selection remain required.

Validation: all 357 tests pass, including stale readiness events and post-hire discovery. Publish SDK 5.13.0 first and install with the matching C-Sweet platform build.

Video Game Director 0.4.6

0.4.6

Use the installation model capacity without hidden per-task output limits. Preserve full supplied collaboration evidence.

Verification: automated regression tests, package version checks and release validation.

Video Game Director 0.4.5

0.4.5

Project-proposal failures are durable manager-owned waits instead of repeated callback exceptions. Director reports the specific next action, preserves the accepted pitch/team/session, and journals one resume only when the current granted broker schema accepts previously rejected root fields. Unchanged errors, cancelled sessions, changed participants, missing pitch authority and turn limits retain their wait. Lost resume responses reuse the saved command; concurrent stale callbacks cannot overwrite a newer wait or restore a cleared one.

Proposal IDs retained in collaboration artifacts are recovered before considering resubmission, including a project already created by an approved proposal. Existing approvals, independent review, staffing and source permissions remain authoritative. No additional capability or network grant is requested.

Uses SDK 5.12.0 and Work Management Contracts 5.3.0. Publish/install with Producer 6.3.2 and restart C-Sweet with the matching broker schema fix. No database migration is required. The existing Super Awesome Games pitch and team can be retained; update through published releases and Installed Agents.

Verification covers corrected/unchanged contracts, repeated wakes, lost responses before/after resume commit, stale callback merges, changed or revoked evidence, cancelled/limited sessions and recovery of a committed proposal from its transcript. See C-Sweet's project-proposal recovery document for verification and live-rollout status.

Video Game Director 0.4.4

0.4.4

Resolve unscoped direct-chat blockers through bounded authorized board reads: exactly one current blocked ticket, board manager, approved project and recorded Producer assignment must agree. Create Director follow-through without fabricating inbound scope or restarting creative intake. Preserve the earlier current-fact incident reporting and scoped-lead routing fixes.

Video Game Director 0.4.3

0.4.3

Accept authenticated reports from the assigned leads of an approved project even when the intake phase cursor has not reached Oversight. Preserve all exact organization, project, team, lead and accepted-pitch checks.

Report the known QA operation mismatch from current facts without claiming broken browser capacity or a completed QA verdict.

Video Game Director 0.4.2

0.4.2

Rename the build-runner choice to Authorize build-runner setup and explain that recording direction does not install or certify capacity. Link setup follow-through to Build runners with the exact business selected. Pausing keeps build work paused; custom answers do not imply setup authorization.

Existing readiness discovery still checks actual certified provider/image eligibility before reporting capacity. Platform administration must install the provider and review/certify the exact environment. The matching C-Sweet UI change recognizes authorized business deep links; no new agent capabilities or grants are requested.

Video Game Director 0.4.1

0.4.1

Recover the retained ready production brief when an older Producer stopped at the four-draft ceiling before structured correction receipts existed. Director attention verifies the exact current project, participants, accepted sources, latest brief and independent creative findings, journals one bounded retry, and resumes the existing collaboration. The resumed Director callback relays the actual candidate-bound corrections instead of repeating the historical blocker.

Pending or paused owner decisions, stale/foreign evidence, cancelled sessions and already bounded corrective failures are never automatically resumed. Lost resume responses are recovered through current-state reads and stable idempotency. No scope, staffing, spending or release approval is manufactured.

Requires Producer 6.2.0 and Creative Director 4.1.0. Publish and update through Installed Agents; no stored-business or installed-payload edits are required.

Video Game Director 0.4.0

0.4.0

Relay exact creative correction receipts to the Producer. Verify a separate project-owned source evidence document against the accepted pitch and GDD before accepting it with the brief; retain both in downstream planning. Preserve independent creative review and delegated authority.

Update Director 0.4.0, Creative Director 4.1.0 and Producer 6.2.0 together through published releases and Installed Agents. Existing completed reviews and legacy briefs remain readable. This release does not rewrite business records or installed runtime payloads.

Video Game Director 0.3.0

0.3.0

Recognize explicitly selected imported games from current owner-accepted project profiles. Retain the imported project ID through the Director/Producer foundation and approved staffing handoff. Preserve normal exact pitch, creative-review, staffing and project-setup decisions; do not create a duplicate game project.

Requires C-Sweet Agent SDK 5.9.0 and the business-first import platform changes. Deploy through the normal published release and Installed Agents update flow.

Video Game Director 0.2.9

0.2.9

• Remove the copied Creative Director delivery-relay and generic coordination paths that escalated routine delivery questions to the CEO.
• Route authenticated, exact-project Creative Director and Producer requests through the existing SDK lead interaction and tracked handoff, without bouncing a discipline request back to its sender.
• Keep unsupported coordination on the governed project artifact/decision and shared SDK incident paths; no raw question manufactures a CEO approval.
• Align the Director's prompts, work titles and portfolio reports with business direction, scope and resources. Naomi retains creative authority and the Producer retains delivery ownership.
• Correct mistaken-request cleanup to stop report tracking only. SDK cancellation does not withdraw execution or cancel another owner's canonical work; already stopped tracking is left alone.