mirror of https://github.com/merlinhu1/codex-game-studio.git synced 2026-08-25 07:54:34 +02:00

Files

T

7e8846a7fb feat: add deterministic model tier routing (#14 )

* feat: add deterministic model tier routing

Define Sol, Terra, and Luna policies with fixed fallbacks, explicit surface assignments, runtime precedence, and Luna escalation. Validate generated metadata and expose tier overrides across role, task, and orchestration commands.

* fix: infer model tiers from surface models

* fix: rebalance prompt model routing

* fix: decouple prompt effort routing

---------

Co-authored-by: MerlinH <merlinh221@gmail.com>

2026-07-10 18:49:20 +10:00

2.5 KiB

Raw Permalink Blame History

model, model_reasoning_effort, primary-agent, linked-skills, phase, risk, argument-hint, source-reference, source-hash, output-artifacts

model

model_reasoning_effort

primary-agent

linked-skills

phase

risk

argument-hint

source-reference

source-hash

output-artifacts

gpt-5.6-luna

medium

qa-playtester

cgs-test-setup

cgs-qa-plan

plan

high

Provide a test setup request with feature scope, target engine/build state, test data, relevant files, owner or handoff needs, and verification evidence.

.codex/workflows/test-setup.md

eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

plan

changed-files

verification-evidence

handoff

Test Setup Workflow

Purpose

Define the test setup for the current feature or milestone, including scenarios, data, environment assumptions, automation hooks, and exit criteria.

Inputs

AGENTS.md
.codex/studio.json
.codex/workflows/test-setup.md
Feature specs, acceptance criteria, build/run commands, and current QA notes

Role

QA Playtester (qa-playtester) owns this workflow.

Taxonomy

Category: qa-testing CCGS adaptation coverage:

test setup
QA environment readiness CLI aliases:
test-setup

Outputs

Test setup checklist with environment, data, scenarios, and pass/fail criteria.
Automation and manual test split.
Risks, blockers, and evidence capture plan.

Validation

Every target behavior has a clear validation route.
Environment assumptions and missing tools are explicit.
Exit criteria are measurable.

Phase Gates

Confirm project state, owner role, write policy, and selected context.
Name required artifacts and acceptance criteria before implementation or review work.
Do not advance to handoff until evidence is recorded or a blocker is explicit.

Required Artifacts

Summary of the workflow result.
Files, assets, tasks, docs, release notes, or tests changed or proposed.
Verification evidence and unresolved risks.

Context Contract

Load AGENTS.md, .codex/studio.json, this workflow, the primary agent, linked skills, and only task-relevant project files.
Avoid broad context unless the user explicitly approves it.

Output Contract

Decision or change summary.
Step-by-step work performed or planned.
Evidence, blockers, warnings, and next owner.

Stop Conditions

Required project state, approval, target files, or verification path is missing.
The task crosses into another role without an explicit handoff.
The workflow would require generated prompt mirrors or hidden automation.

Handoff

Report changed files, validation evidence, residual risks, and the next owner only when ownership changes.

2.5 KiB Raw Permalink Blame History