Video Game QA 2.7.1

2.7.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 QA 2.7.0

2.7.0

Validates every code and artifact task. Runs full story/release regression against complete immutable candidates and returns criterion evidence and actual test output.

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 QA 2.6.0

2.6.0

• Adds durable ticket discussion notifications and directed replies using the shared discussion protocol. Explicit @Full Name: questions request a response; informational notifications do not create reply loops.
• Answers directed ticket questions using current ticket context and recorded review evidence. Responses clarify findings without changing review decisions, acceptance criteria or validation requirements.
• Rereads current authorized state, ignores stale/deleted requests, deduplicates replies and discovers missed questions during bounded attention recovery.
• Requires the C-Sweet ticket discussion host update and approval of the new event subscription/read capabilities.

Video Game QA 2.5.2

2.5.2

• Accept Producer-assigned quality stages when the approved original plan only delegated implementation. Retain canonical role, selection evidence and artifact-package validation; standalone specialist work still requires its original planning delegation.
• Include assignment-denial and platform capability details in blocked QA outcomes so the Producer can identify the actual blocker.
• No validation verdict is accepted without the existing exact-source and executed-test evidence.
• Synchronize the identity self-test with the released package version.

Video Game QA 2.5.1

2.5.1

• Deliverable validation no longer rejects legitimate content as placeholders. Only unmistakable markers
  (TODO:/TBD/FIXME used as markers, lorem ipsum, [insert ...]) count, and fenced or inline code is not
  scanned. A Technical Architecture document that listed "No TODO comments" as a review rule had blocked
  the sprint.
• When its own draft fails validation, a specialist now revises it once with the exact reason before blocking,
  so a fixable output problem no longer stops the sprint.
• No new capabilities or grants.

Video Game QA 2.5.0

2.5.0

• Report criteria can be marked unverifiable when their evidence needs a device, browser, network, registry, service or tool that is unavailable in the QA environment. Unverifiable criteria are never satisfied.
• If every command passes and only unverifiable criteria remain, QA returns Blocked with a decision-required:v1 request naming the criteria, what is missing, and the options (defer or amend, or provide the environment). It no longer returns failed, which sent the unchanged candidate back to engineering with nothing to fix.
• Defects, failing commands, ordinary unmet criteria and any reported finding still fail back to engineering. Findings are reserved for defects; unperformable checks are recorded only as unverifiable criteria. Unverifiable-and-satisfied reports are rejected.
• Includes the unreleased 2.4.9 snapshot-provenance context. No new grants or network access.

Video Game QA 2.4.8

2.4.8

• Match submit_qa_report to the flat named arguments used by the live model. Accept one JSON encoding layer for boolean and array arguments, while retaining compatibility with the previous nested object.
• Reject missing, unknown, ambiguous or incorrectly typed fields without changing the verdict, commands, findings or criterion evidence.
• Return specific tool feedback and the assigned criteria when evidence is invalid, allowing correction without generic tool-error loops.
• Preserve exact-commit, complete-criterion, source-integrity and fixed-report-path checks. Missing desktop performance or bundle measurements remain unmet criteria.

Validation: 46 tests pass on Windows and Linux against published SDK/contracts, including the live string-encoded payload through the full QA harness and correction after rejected evidence. No new platform or network grants are requested.

Video Game QA 2.4.7

2.4.7

• Add a dedicated submit_qa_report tool that writes only the assigned QA report. Report text no longer passes through shell command filtering or a generic file-write approval.
• Allow confined file inspection without unattended approval pauses; general file writes still require approval, and tracked source integrity is still checked before accepting evidence.
• Validate exact commit identity, executed commands, verdict consistency, and every assigned acceptance criterion before saving a report, for both quality stages and standalone QA tickets.
• Report missing or malformed outcome files and unhandled tool approvals explicitly instead of hiding them behind a generic exact-source validation error.
• No platform capability or network grants are added. Missing measurements remain unmet criteria; this update does not approve delivery.

Validation: 37 tests pass against published SDK/contracts; self-test, package build, and Linux agent bundle verified.

Video Game QA 2.4.6

2.4.6

• Download the exact broker-authorized source snapshot into the isolated QA runtime before running validation, using SDK 3.55.0 workspace materialization.
• Verify every original source file against the freshly downloaded snapshot before and after testing. Missing, edited or symlinked source blocks QA; generated local reports do not become source publications.
• Request workspace sync only to download authorized source. QA retains no publish, upload or merge authority, and existing exact-commit validation and review requirements remain.

Video Game QA 2.4.5

2.4.5

Run repository-finalized standalone QA tickets through the existing exact-revision test harness. Require evidence for every assigned acceptance criterion, reject tracked source changes, and submit an exact QA report revision for Producer review. Planning-only tickets retain their document workflow. No new capability grants.