CHARTER: qa/player_cert — the standing certification suite (CI half + box-hosted live half) with roster-complete coverage

[100yenadmin]

From the 2026-07-22 process audit + red-team (roadmap §5.2). Size L. The single highest-leverage anti-regression item.

What: fold walk_test + adventure_walk + journey_eval + the #1647 user-truth stages + a combat-lifecycle probe into ONE tri-state command asserting EVERY certified property.

Architecture (red-team-settled):

• CI half (every PR, ubuntu-runnable): all static/headless assertions — walk_static already covers geometry/manifest; add coherence-report freshness, feature-registry lint, spawn-placement (wire qa/test_seed_spawns.py — currently ZERO CI references, Room Pipeline: spawn placement — open-floor centroid, not first-free-cell #1584), certification sha freshness (test_room_certification, also unwired today).
• Box-hosted live half (named trigger — scheduled box session + owning runbook step): live camera contract, collision accept/reject probes, door cells + painted-arch hotspots cross, actor visible+animated per roster member, silhouette-behind-occluder per roster member, cast tokens present, spawn/arrival on coherence-open cells.
• Version-stamp diff: the owner app self-reports its build stamp on launch; player_cert records the stamp it certified; a diff = LOUD drift warning (kills the 'certified build ≠ installed build' class — the client: runtime-spawned actors bind the animated roster setup (T-pose fix, #1601) #1616-never-reached-the-owner case).
• Roster-complete coverage (F2): live properties iterate the FULL current actor roster; ANY roster addition is a trigger event that re-runs the applicable property set against the new member (the Silhouette pass covers only the last submesh on multi-submesh actors (#1545 follow-up) #1572 decay shape: a new member violates an unstated premise while every existing member passes).
• Build order: the two shared assertion PRIMITIVES first — silhouette-per-submesh + spawn-centroid — consumed immediately by the feat(macos): add native ClawDnD app shell #83 3D spike as exit criteria, aggregated later by the full suite.

Install gate: the owner-install script runs the live half and REFUSES on non-GREEN.

Acceptance: retroactively catches all 8 archaeology cases from the audit (each case maps to a named assertion); a deliberate regression (e.g. WORLDOS_SILHOUETTE=0) turns the suite red.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #1651 - CHARTER: qa/player_cert — the standing certification suite (CI half + box-hosted live half) with roster-complete coverage
State: open

Related issues/PRs: #1647, #1584, #1616, #1572, #83.
Existing labels: enhancement.
Suggested labels: bug, security, docs, tests.
Suggested owners: none.

Related context

• EPIC: USER-TRUTH GATES — the paint the player sees must agree with the game they play (owner playtest 2026-07-22) #1647 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• Room Pipeline: spawn placement — open-floor centroid, not first-free-cell #1584 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• client: runtime-spawned actors bind the animated roster setup (T-pose fix, #1601) #1616 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• Silhouette pass covers only the last submesh on multi-submesh actors (#1545 follow-up) #1572 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• feat(macos): add native ClawDnD app shell #83 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: CHARTER: qa/player_cert — the standing certification suite (CI half + box-hosted live half) with roster-complete coverage - From the 2026-07-22 process audit + red-team (roadmap §5.2). Size L. The single highest-leverage anti-regression item. What: fold walk_test + adventure_walk + journey_eval + the #1647 user-truth stages + a
Product fit: Product/market issue; check vision fit, customer value, and whether external precedent can reduce time-to-market.
Implementation wedge: Start with a bounded adapter/contract or dry-run packet before changing live runtime behavior.

Build / borrow / buy scan:

• Build: identify the smallest implementation wedge that proves the issue without broad rollout.
• Borrow: inspect same-repo prior art, repo memory, GitNexus context, and allowlisted cross-repo examples first.
• Buy/use: run capped external OSS/library/API/current-market research with citations, observed dates, and why each source matters.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.
• Allowlisted cross-repo GitHub examples with direct issue/PR/repo URLs.
• External OSS repositories or library/API docs with freshness dates.
• Current market/product examples, capped and cited, only when they change implementation direction.

Acceptance criteria:

• Preserve and execute the issue's stated acceptance criteria.
• Include source citations for any external OSS/library/current-market claims.
• Keep issue-enrichment comments sticky and idempotent.
• Keep labels, owners, reviewers, and roadmap fields suggestion-only.

Proof plan:

• Focused unit/fixture test for the changed planner behavior.
• Dry-run issue-enrichment evidence packet before live comment posting.
• Redaction check for issue body, citations, and generated markdown.
• Contract or degraded-mode proof before runtime promotion.

Known traps:

• Do not treat related links as proof by themselves; each source needs a reason why it matters.
• Do not scan old issue backlogs or exceed repo-level enrichment throttles.
• External research must stay capped, cited, fresh-dated, and redacted.
• Technical severity alone can miss product/UX regressions; include product-manager review framing.

Non-goals:

• Do not auto-apply labels, owners, reviewers, roadmap fields, or milestones.
• Do not bulk-enrich old backlog issues from this planner output.
• Do not claim external market or OSS research was performed unless cited sources are present.

Context-source taxonomy:

• [enabled] vision_repo_policy_memory_gitnexus: Use repo vision, policy, memory, and GitNexus first before external research.
• [enabled] same_repo_issues_prs: Issue metadata contains same-repo references.
• [enabled] allowlisted_cross_repo_github: Triggered by issue class; keep to configured allowlist and source caps.
• [enabled] external_oss_examples: Use for build/borrow/buy precedent with citations and observed dates.
• [enabled] library_api_docs: Use when implementation may depend on a module, SDK, API, or framework choice.
• [enabled] current_market_examples: Use for product/UX/market positioning issues with freshness dates.
• [enabled] internal_mcp_docs: Use internal docs/MCP context when available; missing context is degraded, not blocking.

Validation suggestions

• Confirm owner, acceptance criteria, and validation evidence before implementation.

Triage gaps

• No obvious issue triage gap detected from issue metadata.

No labels, owners, reviewers, or roadmap fields were changed by this bot.