将 UAIX 项目切换与 OpenAI Agents 和 Codex 结合使用

AGENTS.md
readme.human
.uai/context.uai
.uai/stack.uai
.uai/constraints.uai
.uai/progress.uai
.uai/test-plan.uai

---
uaix: "1.0"
type: agents
project: "Example App"
status: active
---

# Example App

## Handoff Summary
Example App publishes a small web tool. The current task is to update the
settings page without changing authentication, billing, or production deploys.

## Loaded Context
@uai[.uai/context.uai]
@uai[.uai/stack.uai]
@uai[.uai/constraints.uai]
@uai[.uai/progress.uai]
@uai[.uai/test-plan.uai]

## Required First Response
Summarize the project, confirm hard constraints, name expected touchpoints,
and name targeted checks before editing.

---
uaix: "1.0"
type: constraints
title: "Project Constraints"
status: active
---

# Project Constraints

## Hard Rules
- Do not deploy to production without explicit human approval.
- Do not read, print, move, or store secrets.
- Do not change billing, auth, or data-retention behavior unless the task says so.
- Do not make unsupported public support, certification, or endorsement claims.
- Ask before destructive Git or filesystem operations.

## Runtime Policy Inputs
- Treat these constraints as guardrail and approval inputs for OpenAI or any
  other agent runtime.
- If a runtime trace conflicts with these constraints, stop and ask.

---
uaix: "1.0"
type: test-plan
title: "Project Verification Plan"
status: active
---

# Project Verification Plan

## Default
Run targeted checks for the files, routes, commands, and claims changed.

## Full Checks
Run full release, package, launch-surface, locale, and smoke-test sweeps only
for release-scoped work, package builds, broad public-surface changes, or an
explicit human request.

## Report
Final answers must list checks run, checks intentionally skipped, blockers,
and evidence paths.

Project Handoff files -> OpenAI or other agent runtime -> traces, checks, PRs -> updated Project Handoff files