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-sol

high

release-manager

cgs-launch-checklist

cgs-release-checklist

ship

high

Provide a launch checklist request with release target, build/store/comms/support state, rollback needs, owner or handoff needs, and required verification evidence.

.codex/workflows/launch-checklist.md

efefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefef

plan

changed-files

verification-evidence

handoff

Launch Checklist Workflow

Purpose

Prepare launch-day readiness checks across build, store, comms, rollback, support, monitoring, and final go/no-go decisions.

Inputs

AGENTS.md
.codex/studio.json
.codex/workflows/launch-checklist.md
Release checklist, validation output, store requirements, support plan, and rollback notes

Role

Release Manager (release-manager) owns this workflow.

Taxonomy

Category: release-hotfix CCGS adaptation coverage:

launch checklist
launch readiness coordination CLI aliases:
launch-checklist

Outputs

Launch readiness checklist with go/no-go status.
Owners for build, store, comms, support, monitoring, and rollback.
Blockers, warnings, approvals, and final evidence.

Validation

Every launch-critical area has status and owner.
Rollback and support paths are named.
No go/no-go claim appears without evidence.

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