diff --git a/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md b/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md index 99b7388e3..30a1d3a06 100644 --- a/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md +++ b/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md @@ -273,6 +273,13 @@ Current OWNER clarification: - observability integrations - [ ] Charlie - Infrastructure dashboard - [ ] Charlie - Environment validation +- [ ] Charlie - Runtime Reliability implementation + - Current completion percentage: 0%. + - Description: implement the Runtime Reliability Architecture covering resilient page loading, runtime availability events, Admin Logs, runtime logs, future telemetry, correlation IDs, dependency health, retry policies, duplicate suppression, notification routing, resolution lifecycle, diagnostic snapshots, privacy guardrails, and creator-facing runtime failure messaging. + - Remaining work: define event/API/database contracts, implement API-backed runtime availability records, add Admin Logs read model, add privacy-safe diagnostic snapshots, wire System Health aggregation, and add targeted validation. + - Blocking dependencies: PR_26179_001-runtime-reliability-architecture merged. + - Owning team: Team Charlie. + - Cross-team dependency: Team Delta owns future shared runtime/event hook implementation when engine/runtime/shared JS changes are required. - [ ] Charlie - Palette / Colors - Current completion percentage: 40%. - Remaining work: color management, API/database integration, reusable color source of truth, Palette references for Sprites and Objects, and Product Owner testable workflow. diff --git a/docs_build/dev/ProjectInstructions/standards/README.md b/docs_build/dev/ProjectInstructions/standards/README.md index 0d34c10ac..a1a019189 100644 --- a/docs_build/dev/ProjectInstructions/standards/README.md +++ b/docs_build/dev/ProjectInstructions/standards/README.md @@ -8,3 +8,7 @@ Rules: - Generated validation evidence belongs under `docs_build/dev/reports/`. - Historical reference material belongs under the root `archive/` tree. - Reusable PR templates belong under `docs_build/dev/PR/templates/`. + +## Active Architecture Standards + +- Runtime Reliability Architecture: `docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md` diff --git a/docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md b/docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md new file mode 100644 index 000000000..348fe8a64 --- /dev/null +++ b/docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md @@ -0,0 +1,404 @@ +# Runtime Reliability Architecture + +Status: Approved +Owner: OWNER + +## Purpose + +Define the architecture standard for runtime reliability, runtime availability events, admin logs, runtime logs, future telemetry, and creator-facing failure behavior. + +This document is documentation/governance only. It does not implement runtime code, API routes, database schema, browser storage, notification delivery, UI changes, or telemetry providers. + +## Runtime Reliability Overview + +Runtime Reliability is the operational architecture for detecting, classifying, recording, routing, and resolving runtime failures without turning transient runtime state into product data. + +Runtime Reliability covers: + +- page and tool loading failures +- dependency availability failures +- runtime availability events +- admin-readable operational logs +- runtime diagnostic logs +- future telemetry and observability integrations +- creator-facing failure messages + +Runtime Reliability does not own: + +- business events +- audit events +- user analytics +- tool state payloads +- project records +- saved product data +- hidden browser-owned source-of-truth data + +Authoritative runtime reliability records must follow the environment governance model: + +```text +Browser -> API -> Database +``` + +Browser pages may collect transient runtime context and submit it through the API/service contract. Browser pages must not become the authoritative source of runtime reliability records. + +## Resilient Page Loading + +Every user-facing runtime page should have a resilient loading path: + +- initialize a page-load correlation ID before dependency calls begin +- load required static assets deterministically +- validate required runtime dependencies before enabling primary workflows +- show a creator-facing loading, degraded, blocked, or retry state when needed +- avoid blank pages and silent failures +- provide a bounded retry for safe, idempotent dependency reads +- stop retrying when failure is not recoverable or would duplicate writes +- record a runtime availability event for blocked or degraded loading + +Resilient loading must distinguish: + +- blocking failures that prevent the page or primary workflow from running +- non-blocking failures that degrade secondary features +- recoverable failures that can retry safely +- non-recoverable failures that require user or operator action + +## Runtime Availability Events + +Runtime Availability Events are operational records that describe runtime availability, degradation, recovery, and dependency state. + +Minimum event shape for future implementation: + +- `eventId` +- `correlationId` +- `environment` +- `sourcePage` +- `sourceTool` +- `sourceModule` +- `eventType` +- `severity` +- `recoverability` +- `userImpact` +- `healthState` +- `dependency` +- `message` +- `occurredAt` +- `firstSeenAt` +- `lastSeenAt` +- `duplicateCount` +- `resolutionStatus` + +Runtime Availability Events are not Audit Events. If an availability failure also requires an audit trail, a separate Audit Event must be emitted through the Audit Event Contract. + +## Admin Logs Architecture + +Admin Logs are an operator-facing read model for runtime reliability records. + +Admin Logs must: + +- read from API/database-backed operational records +- support filtering by environment, severity, health state, dependency, page, tool, and correlation ID +- separate unresolved, monitoring, resolved, and closed items +- show duplicate-suppression counts and first/last seen timestamps +- link diagnostic snapshots only when snapshots are privacy-safe +- avoid exposing secrets, tokens, credentials, auth session state, or protected user payloads + +Admin Logs must not: + +- rely on browser storage as the source of truth +- rely on page arrays, JSON source files, or `/tmp` files as authoritative data +- mutate runtime behavior directly +- replace System Health or Audit Event records +- expose raw provider internals that belong behind service boundaries + +## Runtime Logs vs Business Events + +Runtime Logs are operational diagnostics. They explain runtime health, page loading, dependency failures, retries, recoveries, and technical context. + +Business Events describe product or user-domain actions such as project creation, publishing, marketplace actions, collaboration, moderation, or account actions. + +Rules: + +- Runtime Logs must not be used as product analytics. +- Business Events must not be inferred from runtime diagnostic logs. +- Audit-required business actions must use the Audit Event Contract. +- Notifications must use the Notification Contract when user/admin delivery is required. +- Runtime Logs may reference business object IDs only when needed for diagnosis and permitted by privacy rules. +- Runtime Logs must avoid storing product payloads. + +## Future Telemetry Architecture + +Future telemetry must be layered behind the runtime reliability API/service contract. + +Telemetry phases: + +1. Runtime Availability Event contract and persistence. +2. Admin Logs read model. +3. System Health aggregation. +4. Diagnostic snapshot collection. +5. Notification routing for operational alerts. +6. External observability provider export. +7. Trend analysis, charts, and reliability service-level indicators. + +Telemetry exports must be optional and environment-managed. The deployable artifact must remain identical across environments; only `.env` or environment-managed secret/configuration values may differ. + +## Severity Classifications + +Runtime reliability severity is operational severity. It is separate from Audit Event severity. + +Allowed runtime severity levels: + +- `debug`: troubleshooting detail that does not indicate a failure. +- `info`: normal operational state or successful recovery. +- `warning`: degraded behavior or recoverable failure. +- `error`: failed runtime behavior requiring attention or visible degradation. +- `critical`: primary workflow unavailable or broad runtime outage. +- `security`: suspected security, authorization, secret, or policy issue. + +Severity must be assigned from observable impact, not from exception text alone. + +## Recoverability Classifications + +Allowed recoverability classifications: + +- `autoRecovered`: the runtime recovered without user or operator action. +- `retryable`: retry may succeed and is safe for the affected operation. +- `userActionRequired`: the user can resolve the condition, such as reconnecting or signing in. +- `operatorActionRequired`: an admin/operator must resolve dependency, configuration, or data issues. +- `nonRecoverable`: the operation cannot continue safely in the current session. + +Recoverability determines retry behavior, creator-facing messaging, and notification routing. + +## User Impact Classifications + +Allowed user impact classifications: + +- `none`: no visible user impact. +- `minor`: secondary feature degraded; primary workflow still works. +- `degraded`: primary workflow works with reduced capability. +- `blocked`: primary workflow cannot continue. +- `dataRisk`: unsaved work, persistence, or integrity may be affected. +- `securityRisk`: security or authorization may be affected. + +User impact must be visible in Admin Logs and must drive creator-facing messaging. + +## Correlation IDs + +Correlation IDs connect page-load events, API calls, dependency checks, runtime logs, diagnostic snapshots, and admin log entries. + +Rules: + +- Create a page-load correlation ID before dependency calls begin. +- Propagate the correlation ID through API calls where supported. +- Include the correlation ID in runtime availability events. +- Include the correlation ID in diagnostic snapshots. +- Show the correlation ID in creator-facing support text only when it helps support triage. +- Do not encode secrets, user identifiers, project payloads, or environment secrets in correlation IDs. + +## Dependency Model + +Runtime reliability must classify dependencies before implementation. + +Dependency categories: + +- `staticAssets`: HTML, CSS, JavaScript, images, and manifest assets. +- `auth`: Supabase Auth and session state. +- `api`: shared API/service contract. +- `database`: Postgres-backed persistence. +- `storage`: Cloudflare R2-backed object storage. +- `runtimeEngine`: engine/runtime modules. +- `toolRuntime`: tool bootstrap and hosted tool context. +- `externalProvider`: external service or provider integration. +- `browserCapability`: browser APIs required for the current workflow. + +Dependency records must identify whether the dependency is required, optional, degraded-capable, retryable, or environment-managed. + +## Retry Policies + +Retry must be bounded and safe. + +Rules: + +- Retry only idempotent reads or explicitly safe operations. +- Use bounded exponential backoff with jitter for retryable dependency reads. +- Stop retrying when the operation is non-recoverable. +- Do not retry writes that could duplicate product data unless the API provides idempotency keys. +- Do not hide persistent failures behind endless retries. +- Emit one availability event for the failure group and update duplicate counts instead of logging each retry as a new incident. +- Surface creator-facing retry controls only when the user can safely retry. + +## Health States + +Allowed health states: + +- `healthy`: expected behavior is available. +- `degraded`: feature is available with reduced capability. +- `partialOutage`: one or more required dependencies are unavailable while other areas still work. +- `unavailable`: primary workflow cannot run. +- `maintenance`: planned operator action limits availability. +- `unknown`: health cannot be determined. + +Health states must be derivable from runtime availability events and dependency state. + +## Duplicate Suppression + +Duplicate suppression prevents noisy repeated failures from flooding Admin Logs and notifications. + +Rules: + +- Compute a stable failure fingerprint from source, dependency, event type, severity, recoverability, and sanitized message category. +- Group duplicates within a bounded time window. +- Preserve `firstSeenAt`, `lastSeenAt`, and `duplicateCount`. +- Preserve the latest safe diagnostic summary. +- Escalate if severity or user impact increases. +- Do not suppress distinct correlation IDs when they indicate separate user-impacting sessions that require triage. + +## Notification Routing + +Notification routing decides who receives operational alerts. + +Default routes: + +- `debug` and `info`: Admin Logs only. +- `warning`: Admin Logs; System Health aggregation when repeated or dependency-wide. +- `error`: Admin Logs and System Health; notify operators when unresolved or repeated. +- `critical`: Admin Logs, System Health, and operator notification. +- `security`: Admin Logs, security/audit review path, and operator notification. + +Creator-facing notifications must be limited to actionable, user-safe information. They must not expose internal dependency names, stack traces, secrets, SQL errors, provider details, or protected operational internals. + +## Resolution Lifecycle + +Allowed resolution lifecycle states: + +- `detected`: event captured and recorded. +- `triaged`: owner, dependency, and impact classification reviewed. +- `mitigated`: workaround or retry restored user workflow, but root cause may remain. +- `monitoring`: recovery observed and duplicates monitored. +- `resolved`: root cause or configuration issue resolved. +- `closed`: no further action required and retention policy applies. + +Resolution records should include: + +- owner +- status +- resolution summary +- mitigation summary +- linked correlation IDs +- linked diagnostic snapshots +- timestamps for state changes + +## Diagnostic Snapshots + +Diagnostic snapshots are privacy-safe operational summaries captured for triage. + +Allowed content: + +- correlation ID +- environment +- page/tool/module identifiers +- dependency status +- sanitized error category +- retry count +- timing summary +- health state +- browser capability summary + +Prohibited content: + +- secrets, tokens, credentials, cookies, or auth provider session state +- raw SQL, stack traces containing secrets, or provider internals +- tool payloads, project records, product data, or user-generated content +- file bytes or image data URLs +- payment state or protected marketplace transaction details + +Large snapshots may be stored in R2 only through server/API ownership with privacy-safe metadata in Postgres. + +## Privacy Requirements + +Runtime reliability records must follow privacy-by-default rules: + +- collect the minimum data needed for diagnosis +- sanitize messages before persistence +- avoid user-generated payloads +- avoid browser-owned product data +- avoid secrets and credentials +- use stable identifiers only when required for support or triage +- enforce retention and deletion policy before external telemetry export +- separate operational diagnostics from business analytics + +## Creator-facing Messaging Guidelines + +Creator-facing messaging should be calm, actionable, and safe. + +Messages should: + +- name what is affected in user terms +- say whether the user can retry +- preserve unsaved work where possible +- provide a support-safe correlation ID when useful +- avoid blame or internal provider details +- avoid stack traces and implementation names +- distinguish temporary degradation from blocked workflows + +Example message patterns: + +- "This tool could not finish loading. Try again, or contact support with reference {correlationId}." +- "Some runtime services are delayed. You can keep editing, but saving may be unavailable until the connection recovers." +- "This action is temporarily unavailable. Your current page remains open." + +## Blocking vs Non-Blocking Failures + +Blocking failures prevent the page or primary workflow from continuing safely. + +Examples: + +- authentication unavailable for a protected workflow +- API unavailable for required product data +- database write unavailable for a save operation +- required runtime module failed to load +- required project/tool state cannot be read + +Non-blocking failures degrade secondary behavior while preserving the primary workflow. + +Examples: + +- optional preview unavailable +- non-required telemetry export unavailable +- delayed health aggregation +- optional notification delivery failure +- degraded chart or admin summary view + +Blocking status must be visible to the creator. Non-blocking status may be visible through subtle degraded-state messaging and Admin Logs. + +## Runtime Logging Lifecycle + +Runtime logging lifecycle: + +1. Capture transient browser/runtime context. +2. Normalize into a safe runtime event envelope. +3. Attach correlation ID and dependency classification. +4. Classify severity, recoverability, user impact, and health state. +5. Suppress duplicates. +6. Submit through the API/service contract. +7. Persist authoritative records in the database. +8. Route to Admin Logs, System Health, notification queues, or future telemetry exporters. +9. Resolve through the resolution lifecycle. +10. Retain, archive, or delete according to privacy and operational retention rules. + +Browser capture is transient. The database-backed record is authoritative. + +## Future Observability Roadmap + +Future implementation should proceed in small PRs: + +1. Runtime Availability Event contract and validation. +2. API/database persistence for availability events. +3. Runtime page-load correlation ID standard. +4. Resilient page loading hooks for selected high-value pages. +5. Admin Logs read model. +6. Duplicate suppression and resolution lifecycle. +7. Diagnostic snapshot capture with privacy guardrails. +8. System Health aggregation from runtime availability records. +9. Notification routing for critical and security events. +10. External telemetry exporter behind environment-managed configuration. + +No future observability work may introduce browser-owned product data, mock repositories as completion state, or environment-specific runtime code. diff --git a/docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md b/docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md index 6341fdf34..9e32c5911 100644 --- a/docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md +++ b/docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md @@ -33,7 +33,7 @@ If a team has no assignment, no active branch, and no active PR, it is inactive | Team Charlie | none | none | none | Available | Active ownership lane | | Team Delta | PR_26177_DELTA_056-shared-validation-assertions | PR_26177_DELTA_056-shared-validation-assertions | PR_26177_DELTA_056-shared-validation-assertions | Active | OWNER override approved: Continue Team Delta random utility stack with PR_26177_DELTA_056-shared-validation-assertions | | Team Golf | none | none | none | Available | Replacement active ownership lane for retired Team Gamma | -| Team OWNER | none | none | none | Available | Governance Phase 1 complete | +| Team OWNER | PR_26179_001-runtime-reliability-architecture | PR_26179_001-runtime-reliability-architecture | PR_26179_001-runtime-reliability-architecture | Active | OWNER-assigned documentation/governance architecture PR | ## Current Active Ownership Lanes diff --git a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md index e7826a808..2cee356ca 100644 --- a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md +++ b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md @@ -15,7 +15,7 @@ This file records active assignments and registry state. Workflow summaries here | Team Charlie | none | none | none | Available | | Team Delta | PR_26177_DELTA_056-shared-validation-assertions | PR_26177_DELTA_056-shared-validation-assertions | PR_26177_DELTA_056-shared-validation-assertions | Active | | Team Golf | none | none | none | Available | -| Team OWNER | none | none | none | Available | +| Team OWNER | PR_26179_001-runtime-reliability-architecture | PR_26179_001-runtime-reliability-architecture | PR_26179_001-runtime-reliability-architecture | Active | Rules: - Registry is the authoritative active-work view. @@ -100,11 +100,13 @@ OWNER decision: Replacement active ownership lane for retired Team Gamma. ## Team OWNER -Status: Available +Status: Active -Active assignment: none. +Active assignment: PR_26179_001-runtime-reliability-architecture. -Active branch: none. +Active branch: PR_26179_001-runtime-reliability-architecture. + +Active PR: PR_26179_001-runtime-reliability-architecture. ## Team Name Registry diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md new file mode 100644 index 000000000..4c9f6984e --- /dev/null +++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md @@ -0,0 +1,34 @@ +# PR_26179_001-runtime-reliability-architecture + +Date: 2026-06-27 12:32:39 +Team: OWNER +Branch: PR_26179_001-runtime-reliability-architecture +Base HEAD: 1642cfb041a55c70e7e6e9f661a43e916210fde8 +Scope: Documentation/governance-only runtime reliability architecture +Status: PASS + +## Summary + +- Added Runtime Reliability Architecture under ProjectInstructions standards. +- Indexed the architecture document from the standards README. +- Added a Team Charlie implementation backlog item with Team Delta dependency noted for future runtime/shared JS hooks. +- Updated active OWNER planning records for this PR branch. +- No runtime/product/API/database implementation changed. + +## Deliverables + +- docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md +- docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md +- docs_build/dev/ProjectInstructions/standards/README.md +- docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md +- docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md +- docs_build/dev/reports/codex_review.diff +- docs_build/dev/reports/codex_changed_files.txt +- docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md +- docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md +- docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md +- tmp/PR_26179_001-runtime-reliability-architecture_delta.zip + +## Product Owner Review + +This PR is documentation-only. The Product Owner can review the Runtime Reliability Architecture and the new backlog item for future implementation ownership. diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_branch-validation.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_branch-validation.md new file mode 100644 index 000000000..3cac7dcc2 --- /dev/null +++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_branch-validation.md @@ -0,0 +1,8 @@ +# Branch Validation - PR_26179_001-runtime-reliability-architecture + +Status: PASS + +- PASS: Started from synchronized main before branch creation. +- PASS: Current branch is PR_26179_001-runtime-reliability-architecture. +- PASS: Branch is not main for implementation, validation, commit, and push. +- PASS: Work remains tied to PR identity PR_26179_001-runtime-reliability-architecture. diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_manual-validation-notes.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_manual-validation-notes.md new file mode 100644 index 000000000..723eabdd5 --- /dev/null +++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_manual-validation-notes.md @@ -0,0 +1,8 @@ +# Manual Validation Notes - PR_26179_001-runtime-reliability-architecture + +Status: PASS + +- Reviewed active ProjectInstructions before editing. +- Confirmed ProjectInstructions standards is the appropriate active owner for the architecture document. +- Confirmed Team Charlie is the implementation owner because Runtime, System Health, Environment Management, and Operations are Charlie-owned; Team Delta dependency is noted for future runtime/shared JS hooks. +- Confirmed this PR does not implement runtime code, API routes, database schema, UI, browser storage, or telemetry providers. diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md new file mode 100644 index 000000000..691ba880c --- /dev/null +++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md @@ -0,0 +1,29 @@ +# Requirement Checklist - PR_26179_001-runtime-reliability-architecture + +Status: PASS + +- PASS: Documentation only. +- PASS: Runtime Reliability overview documented. +- PASS: Resilient Page Loading documented. +- PASS: Runtime Availability Events documented. +- PASS: Admin Logs architecture documented. +- PASS: Runtime Logs vs Business Events documented. +- PASS: Future Telemetry architecture documented. +- PASS: Severity classifications documented. +- PASS: Recoverability classifications documented. +- PASS: User impact classifications documented. +- PASS: Correlation IDs documented. +- PASS: Dependency model documented. +- PASS: Retry policies documented. +- PASS: Health states documented. +- PASS: Duplicate suppression documented. +- PASS: Notification routing documented. +- PASS: Resolution lifecycle documented. +- PASS: Diagnostic snapshots documented. +- PASS: Privacy requirements documented. +- PASS: Creator-facing messaging guidelines documented. +- PASS: Blocking vs non-blocking failures documented. +- PASS: Runtime logging lifecycle documented. +- PASS: Future observability roadmap documented. +- PASS: Backlog item created for implementation ownership. +- PASS: No implementation changes. diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md new file mode 100644 index 000000000..2a03e96eb --- /dev/null +++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md @@ -0,0 +1,22 @@ +# Validation Report - PR_26179_001-runtime-reliability-architecture + +Status: PASS + +## Commands + +- git branch --show-current +- git status --short --branch --untracked-files=all +- git rev-list --left-right --count main...origin/main before branch creation +- Section scan for required Runtime Reliability Architecture topics +- Changed path scope scan for documentation/governance-only files +- git diff --check + +## Results + +- Branch: PR_26179_001-runtime-reliability-architecture +- Required architecture topics present: 22/22 +- Backlog implementation ownership item present: PASS +- Non-doc/governance changed paths: 0 +- start_of_day changed paths: 0 +- Runtime/product/API/database files changed: 0 +- Playwright: not run; no runtime files changed. diff --git a/docs_build/dev/reports/codex_changed_files.txt b/docs_build/dev/reports/codex_changed_files.txt index 4c7d9fba2..4ebd2023e 100644 --- a/docs_build/dev/reports/codex_changed_files.txt +++ b/docs_build/dev/reports/codex_changed_files.txt @@ -1,22 +1,12 @@ -docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md -docs_build/dev/ProjectInstructions/README.txt -docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md -docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md -docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md -docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md -docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md -docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md -docs_build/dev/ProjectInstructions/addendums/multi_team.md -docs_build/dev/ProjectInstructions/addendums/pr_workflow.md -docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md -docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md -docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md -docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md -docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md -docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization.md -docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_branch-validation.md -docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_manual-validation-notes.md -docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_requirements-checklist.md -docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_validation-lane.md -docs_build/dev/reports/codex_changed_files.txt -docs_build/dev/reports/codex_review.diff +M docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md +M docs_build/dev/ProjectInstructions/standards/README.md +A docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md +M docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md +M docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md +A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md +A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_branch-validation.md +A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_manual-validation-notes.md +A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md +A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md +M docs_build/dev/reports/codex_changed_files.txt +M docs_build/dev/reports/codex_review.diff diff --git a/docs_build/dev/reports/codex_review.diff b/docs_build/dev/reports/codex_review.diff index d3746d2fa..97707eca8 100644 --- a/docs_build/dev/reports/codex_review.diff +++ b/docs_build/dev/reports/codex_review.diff @@ -1,1768 +1,653 @@ -diff --git a/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md b/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md -index d6617c986..ffd6f2438 100644 ---- a/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md -+++ b/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md -@@ -58,6 +58,20 @@ Existing Project Instructions outside `docs_build/dev/ProjectInstructions/` rema - - `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` defines required Start of Day team briefings, End of Day team summaries, active team backlog fields, completion percentage update points, backlog-driven next PR selection, and official military team-name spelling. - -+## Canonical Governance Owners -+ -+When active guidance overlaps, use these canonical owner documents: -+ -+- Workflow and Product Owner testable completion: `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md` -+- START / WORK / END lifecycle, branch gates, mandatory hard stops, and EOD main lock: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` -+- Page-level Playwright organization and completion coverage: `docs_build/dev/ProjectInstructions/addendums/test_structure_standardization.md` -+- API/environment model and `Browser -> API -> Database` rule: `docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md` -+- Environment variable, URL, R2 prefix, and feature flag configuration: `docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md` -+- Team backlog fields, completion percentages, and next logical PR ownership: `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` -+- Team ownership and assignment routing: `docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md` -+ -+Other active addendums may summarize these rules, but they must point back to the canonical owner document and must not create a competing active rule. -+ - ## Environment Governance - - `docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md` defines the official environment model, environment invariance rule, shared API/service contract rule, required Supabase/Postgres/R2 services, required R2 prefixes, and SQLite retired status. -@@ -97,7 +111,7 @@ OWNER override wording: - `OWNER override approved: ` - - OWNER follows the same safety rules: --- One active Team OWNER branch at a time. -+- Team OWNER follows the same one-active-branch discipline as every team. - - One active OWNER assignment at a time. - - OWNER may override team locks, but may not silently delete, rewrite, or remove protected instructions. - - OWNER override must be explicitly documented. -diff --git a/docs_build/dev/ProjectInstructions/README.txt b/docs_build/dev/ProjectInstructions/README.txt -index 1b647c6fd..bbfff9812 100644 ---- a/docs_build/dev/ProjectInstructions/README.txt -+++ b/docs_build/dev/ProjectInstructions/README.txt -@@ -16,7 +16,7 @@ No direct commits to main: - Do not commit directly to main. Normal work must use PR branches, draft PRs, validation evidence, and owner-controlled merge approval. - - Branch lifecycle: --Every PR follows exactly three phases: START, WORK, END. The canonical lifecycle is `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -+The canonical START / WORK / END lifecycle is `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. - - OWNER override rule: - An OWNER override must use this wording: -diff --git a/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md b/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md -index 5fe1c43e4..7f9bcad29 100644 ---- a/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md -+++ b/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md -@@ -13,14 +13,7 @@ Use `docs_build/dev/ProjectInstructions/` as the only active Project Instruction - Read `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` before implementation. - - Branch Lifecycle (Canonical): --- Every PR follows exactly three phases: START, WORK, END. --- Follow `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. --- START begins on synchronized `main` and creates the PR branch only after all gates pass. --- WORK remains on the PR branch. Never checkout `main`. --- END merges, returns to synchronized `main`, publishes branch, HEAD SHA, and date/time, then stops all work. --- No commits on `main`. --- No implementation on `main`. --- No validation on `main` except start validation. -+- Follow `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` for START / WORK / END lifecycle, branch gates, mandatory hard stops, and EOD main lock. - - ## Start Team Alfa - -diff --git a/docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md b/docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md -index 798bb2cba..a829b0a15 100644 ---- a/docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md -+++ b/docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md -@@ -7,6 +7,10 @@ Owner: OWNER - - Require Codex and teams to confirm branch context before changing files. - -+Canonical branch lifecycle reference: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -+ -+This file owns branch context confirmation and stop conditions; it must not create a competing START / WORK / END lifecycle rule. -+ - ## Session Start Context - - At the start of work, report or validate: -diff --git a/docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md b/docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md -index 6f797306d..1851906ab 100644 ---- a/docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md -+++ b/docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md -@@ -7,6 +7,10 @@ Owner: OWNER - - Keep active work attached to the correct assigned team, branch, and OWNER decision. - -+Canonical branch lifecycle reference: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -+ -+This file owns branch lock enforcement and OWNER override handling; it must not create a competing START / WORK / END lifecycle rule. -+ - ## Active Work Lock - - - Work must occur on the active team branch. -@@ -39,21 +43,13 @@ Keep active work attached to the correct assigned team, branch, and OWNER decisi - - ## Branch Lifecycle (Canonical) - --Every PR follows exactly three phases: -+The canonical branch lifecycle lives in: - - ```text --START --WORK --END -+docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md - ``` - --The canonical lifecycle lives in `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -- --Branch lock governance enforces: --- START on synchronized `main`. --- WORK only on the PR branch. --- END by merging, returning to synchronized `main`, publishing branch, HEAD SHA, and date/time, then stopping all work. --- Mandatory hard stops before commits on `main`, dirty branch creation, non-`0 0` main sync, baseline SHA mismatch, unvalidated merge, or new unrelated workstream before synchronized main return. -+Branch lock governance enforces ownership and branch-lock compliance with that canonical lifecycle. - - ## OWNER Override - -diff --git a/docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md b/docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md -index 17be32ada..a382a65df 100644 ---- a/docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md -+++ b/docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md -@@ -55,7 +55,7 @@ Codex responses must include: - Every tool MVP PR report must include: - - Product Owner testable outcome - - What Playwright tests --- What Mr. Q should manually test -+- What the Product Owner should manually test - - Whether the PR is part of a stacked MVP sequence - - Previous PR dependency - - Next PR dependency -@@ -63,7 +63,7 @@ Every tool MVP PR report must include: - The report must answer: - - ```text --What can Mr. Q test after applying this ZIP? -+What can the Product Owner test after applying this ZIP? - ``` - - If a tool MVP PR has no Playwright lane, the report must state why and list the manual Product Owner validation instead. -diff --git a/docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md b/docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md -index c6d8f192c..daf35f1d3 100644 ---- a/docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md -+++ b/docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md -@@ -23,25 +23,13 @@ Codex must use this as the only active source of truth for: - - ## Branch Lifecycle Start Gate - --Every PR follows exactly three phases: -+Codex must follow the canonical lifecycle in: - - ```text --START --WORK --END -+docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md - ``` - --Codex must follow the canonical lifecycle in: -- --`docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` -- --Startup enforcement: --- START begins on synchronized `main`. --- WORK remains on the PR branch. Never checkout `main`. --- END merges, returns to synchronized `main`, publishes branch, HEAD SHA, and date/time, then stops all work. --- STOP if current branch is `main` before commit. --- STOP if attempting to push `main`. --- STOP if a new PR starts before returning to synchronized `main`. -+This startup addendum only requires Codex to read and apply that canonical lifecycle; it must not define a competing lifecycle rule. - - Deprecated Project Instructions material outside `docs_build/dev/ProjectInstructions/` is reference-only and must not override active governance. - -diff --git a/docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md b/docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md -index 5a91f904c..414bf9758 100644 ---- a/docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md -+++ b/docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md -@@ -11,6 +11,10 @@ This addendum is governance/documentation only. It does not change runtime behav - - ## Source Model - -+Canonical environment/API model reference: `docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md`. -+ -+This file owns environment variable names, URL configuration, R2 prefix configuration, and feature flag configuration only. -+ - This standard builds on: - - ```text -@@ -88,12 +92,10 @@ R2 project, backup, export, import, or future storage paths must stay under the - - ## API/Service Contract Configuration - --One shared API/service contract is required across Local (VS Code), DEV, IST, UAT, and PROD. -+The canonical shared API/service contract rule lives in `docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md`. - --Rules: -+This section owns configuration-only API URL requirements: - --- Browser/UI/runtime code must follow `Browser -> API -> Database` for authoritative product data. --- `Local API` means the same shared API/service contract running locally, not a separate local-only API implementation. - - API URLs may differ by `.env` only. - - Do not split Local API and Public API contracts. - - Do not create environment-specific API/service contracts. -diff --git a/docs_build/dev/ProjectInstructions/addendums/multi_team.md b/docs_build/dev/ProjectInstructions/addendums/multi_team.md -index 7ba2cae8d..763dccc8a 100644 ---- a/docs_build/dev/ProjectInstructions/addendums/multi_team.md -+++ b/docs_build/dev/ProjectInstructions/addendums/multi_team.md -@@ -1,5 +1,11 @@ - # Multi-Team Codex Execution Governance - -+Canonical workflow reference: `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md`. -+ -+Canonical branch lifecycle reference: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -+ -+This file owns multi-team execution coordination and must not create competing workflow or branch lifecycle rules. -+ - ## Four Active Delivery Teams - - The single authoritative four-team ownership definition is: -@@ -65,7 +71,7 @@ Rules: - ## Day Work / EOD Merge Rule - - During active work: --- Work happens on assigned team branches, OWNER branches, or scoped PR branches. -+- Work happens on active non-main team branches or scoped PR branches. - - Commits are allowed only on assigned non-main branches. - - Pushes are allowed and expected. - - Draft PRs are allowed and expected. -diff --git a/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md b/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md -index bee8bdd75..97a73ca30 100644 ---- a/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md -+++ b/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md -@@ -46,31 +46,11 @@ This section supersedes older active wording that implies returning to `main` be - - ## Branch Lifecycle (Canonical) - --Every PR follows exactly three phases: -- --```text --START --WORK --END --``` -- - The canonical START, WORK, END, Daily Synchronization, and Mandatory Hard Stops rules live in: - - `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` - --PR workflow must follow that lifecycle exactly. -- --Summary: --- START happens on synchronized `main` only and creates the PR branch only after all required gates pass. --- WORK happens only on the PR branch. --- END validates, commits, pushes, opens/updates the PR, merges, returns to synchronized `main`, publishes branch, HEAD SHA, and date/time, then stops all work. --- No commits on `main`. --- No implementation on `main`. --- No validation on `main` except start validation. --- Never checkout `main` during WORK. --- STOP before commit if current branch is `main`. --- STOP if current branch changes unexpectedly. --- STOP if attempting to push `main`. -+PR workflow must follow that lifecycle exactly and must not create a competing lifecycle rule. - - ## PR Lifecycle States - -@@ -153,7 +133,7 @@ Do not stop after every small PR unless blocked by branch state, failed validati - Each tool MVP PR plan or template must include: - - Product Owner testable outcome - - What Playwright tests --- What Mr. Q should manually test -+- What the Product Owner should manually test - - Whether the PR is part of a stacked MVP sequence - - Previous PR dependency - - Next PR dependency -@@ -162,6 +142,8 @@ Visible acceptance must be Creator-facing first. Architecture can be handled und - - ## Product Owner Testable Definition - -+Canonical owner: this section is the active canonical Product Owner testable completion rule. -+ - A request to complete a page, tool, MVP, or testable experience means Product Owner testable by default. Codex must deliver a working Product Owner testable feature, not a shell or foundation page, unless the Product Owner explicitly requests a shell/foundation PR. - - A Product Owner testable outcome means the Product Owner can: -diff --git a/docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md b/docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md -index be3555469..e6d6c7ce8 100644 ---- a/docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md -+++ b/docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md -@@ -42,14 +42,15 @@ Each backlog item must track: - - current completion percentage - - remaining work - - blocking dependencies -+- owning team - - Completion percentages are updated: - - - at SOD --- after each accepted PR -+- after every accepted PR - - at EOD - --The backlog is the authoritative source for determining the next PRs. -+The backlog is the authoritative source for determining the next logical PRs. - - If the backlog and a generated report conflict, the backlog wins unless OWNER explicitly approves a newer governance decision. - -diff --git a/docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md b/docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md -index 2bcc52a60..5da2f9952 100644 ---- a/docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md -+++ b/docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md -@@ -24,7 +24,7 @@ One large Codex command -> multiple focused stacked PRs -> each PR has a Product - - Each PR must answer: - - ```text --What can Mr. Q test after applying this ZIP? -+What can the Product Owner test after applying this ZIP? - ``` - - - Codex must continue through the stacked PR sequence unless blocked by: -@@ -40,45 +40,14 @@ For tool MVP PR planning, visible acceptance must be Creator-facing first. - - Architecture can be handled under the covers, but PR purpose must be user-testable. - --A request to complete a page, tool, MVP, or testable experience means Product Owner testable by default. Codex must deliver a working Product Owner testable feature, not a shell or foundation page, unless the Product Owner explicitly requests a shell/foundation PR. -- --A Product Owner testable outcome means the Product Owner can: -- --- open the page/tool --- perform the primary workflow --- save/load data where applicable --- observe expected results --- validate success and failure states --- follow manual validation steps from the PR report -- --Not acceptable as complete/testable: -- --- shell-only page --- route-only page --- navigation-only PR --- template-only page --- placeholder controls --- static table with no workflow --- `Not implemented yet` --- `coming soon` --- placeholder-only workspace, inspector, or output sections --- planned-only tile --- route that loads but cannot be used -- --Required for Product Owner testable completion: -- --- visible working controls --- API-backed data where required --- validation and error states --- empty states --- save/load behavior where applicable --- manual validation steps for Product Owner --- targeted Playwright coverage where impacted. -+Canonical reference: `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md` owns the Product Owner testable definition and no-shell completion rule. -+ -+Canonical Playwright reference: `docs_build/dev/ProjectInstructions/addendums/test_structure_standardization.md` owns page-level Playwright organization and minimum completion coverage. - - Each tool MVP PR must state: - - Product Owner testable outcome - - What Playwright tests --- What Mr. Q should manually test -+- What the Product Owner should manually test - - Whether the PR is part of a stacked MVP sequence - - Previous PR dependency - - Next PR dependency diff --git a/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md b/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md -index cc9ddc88c..99b7388e3 100644 +index 99b7388e3..30a1d3a06 100644 --- a/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md +++ b/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md -@@ -2,19 +2,22 @@ - - ## Backlog Item Tracking Standard - -+Canonical backlog tracking owner: `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md`. -+ - Every active team owns an active backlog when it has assigned work. - --Each backlog item must track: -+Backlog entries in this file follow the canonical field list, including: - - - Name - - Description - - Current completion percentage - - Remaining work - - Blocking dependencies -+- Owning team - --Completion percentages are updated at SOD, after each accepted PR, and at EOD. -+Completion percentages are updated at SOD, after every accepted PR, and at EOD. - --The backlog is the authoritative source for determining the next PRs. -+The backlog is the authoritative source for determining the next logical PRs. - - ## Game Journey MVP - -@@ -44,10 +47,13 @@ The backlog is the authoritative source for determining the next PRs. - - [ ] Bravo - Asset Studio V2 - - [ ] Charlie - Sprites canvas editor MVP - - Sprites is a creator tool, not only an asset metadata library. -- - MVP requires canvas/grid editor behavior, width/height controls, Palette/Colors-only reusable colors, color selection from Palette/Colors, pixel painting, save/load sprite grid data through the API/database, and Product Owner manual validation. -+ - 5% Complete. -+ - Remaining work: canvas/grid editor, width/height controls, Palette/Colors-only color selection, pixel painting, save/load sprite grid data through API/database, Product Owner testable workflow, and remove Category from Sprites planning. - - Category is removed from Sprites MVP planning. - - [ ] Bravo - Animation Studio V2 --- [ ] Bravo - Palette Manager -+- [ ] Charlie - Palette / Colors -+ - 40% Complete. -+ - Remaining work: color management, API/database integration, reusable color source of truth, Palette references for Sprites and Objects, and Product Owner testable workflow. - - [ ] Bravo - Video Studio - - ### Audio -@@ -65,7 +71,10 @@ The backlog is the authoritative source for determining the next PRs. - - 0% Complete — Create the things players interact with - --- [ ] Alfa - Objects -+- [ ] Charlie - Objects -+ - 0% Complete. -+ - Objects includes object library, object editor, Sprite assignment, object properties, collision configuration, runtime object metadata, and Object API/database contracts. -+ - Remaining work: object library, object editor, Sprite assignment, object properties, collision configuration, runtime object metadata, Object API/database contracts, and Product Owner testable workflow. - - [ ] Alfa - Characters - - [ ] Alfa - Object Behaviors - -@@ -226,6 +235,13 @@ Current OWNER clarification: - - ### Team Charlie - -+- Active ownership: Runtime, System Health, Environment Management, Palette / Colors, Sprites, Objects. -+- Runtime: 100% Complete. -+- System Health: 100% Complete. -+- Environment Management: 100% Complete. -+- Palette / Colors: 40% Complete. -+- Sprites: 5% Complete. -+- Objects: 0% Complete. - - [ ] Charlie - Guardrail hardening - - [ ] Charlie - Browser validation hardening - - [ ] Charlie - Remaining test relocation audit -@@ -257,6 +273,15 @@ Current OWNER clarification: +@@ -273,6 +273,13 @@ Current OWNER clarification: - observability integrations - [ ] Charlie - Infrastructure dashboard - [ ] Charlie - Environment validation -+- [ ] Charlie - Palette / Colors -+ - Current completion percentage: 40%. -+ - Remaining work: color management, API/database integration, reusable color source of truth, Palette references for Sprites and Objects, and Product Owner testable workflow. -+- [ ] Charlie - Sprites canvas editor MVP -+ - Current completion percentage: 5%. -+ - Scope: canvas/grid editor, width/height controls, Palette/Colors-only color selection, pixel painting, save/load sprite grid data through API/database, Product Owner testable workflow, and remove Category from Sprites planning. -+- [ ] Charlie - Objects ++- [ ] Charlie - Runtime Reliability implementation + - Current completion percentage: 0%. -+ - Scope: object library, object editor, Sprite assignment, object properties, collision configuration, runtime object metadata, Object API/database contracts, and Product Owner testable workflow. - - ### Team Delta - -diff --git a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md -index 4253971d9..e7826a808 100644 ---- a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md -+++ b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md -@@ -1,5 +1,11 @@ - # TEAM_ASSIGNMENTS - -+Canonical workflow reference: `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md`. -+ -+Canonical branch lifecycle reference: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -+ -+This file records active assignments and registry state. Workflow summaries here are subordinate to the canonical workflow and branch lifecycle documents. -+ - # Active Team Registry - - | Team | Assignment | Branch | PR | Status | -@@ -197,7 +203,7 @@ Conflict note: - ## Day Work / EOD Merge Rule - - During active work: --- Work happens on assigned team branches, OWNER branches, or scoped PR branches. -+- Work happens on active non-main team branches or scoped PR branches. - - Commits are allowed only on assigned non-main branches. - - Pushes are allowed and expected. - - Draft PRs are allowed and expected. -@@ -263,23 +269,10 @@ Teams must use only `docs_build/dev/ProjectInstructions/` as the active Project - - ## Branch Lifecycle (Canonical) - --Every PR follows exactly three phases: -+Teams must follow the canonical branch lifecycle in: - - ```text --START --WORK --END -+docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md - ``` - --Teams must follow `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -- --Assignment governance enforces: --- START begins on synchronized `main`. --- WORK remains on the PR branch. Never checkout `main`. --- END merges, returns to synchronized `main`, publishes branch, HEAD SHA, and date/time, then stops all work. --- No commits on `main`. --- No implementation on `main`. --- No validation on `main` except start validation. --- STOP if current branch is `main` before commit. --- STOP if attempting to push `main`. --- STOP if new PR work starts before returning to synchronized `main`. -+Assignment governance records active team and branch state; it must not create a competing lifecycle rule. -diff --git a/docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md b/docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md -index 30b4f2dfe..0655d6a95 100644 ---- a/docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md -+++ b/docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md -@@ -30,11 +30,14 @@ This section is the current OWNER-approved active ownership alignment. - - Repository compliance - - Validation - - Infrastructure -+- Runtime - - Storage --- Environment management -+- Environment Management - - System Health - - Operations -+- Palette / Colors - - Sprites canvas editor MVP -+- Objects - - Team Charlie System Health owns: - - Environment Summary -@@ -45,9 +48,25 @@ Team Charlie System Health owns: - - Team Charlie Sprites ownership: - - Sprites is a creator tool, not only an asset metadata library. --- Sprites MVP requires canvas/grid editor behavior, width/height controls, Palette/Colors-only reusable colors, color selection from Palette/Colors, pixel painting, save/load sprite grid data through the API/database, and Product Owner manual validation. -+- Sprites MVP requires canvas/grid editor behavior, width/height controls, Palette/Colors-only color selection, pixel painting, save/load sprite grid data through API/database, and a Product Owner testable workflow. - - Sprites must not own reusable color definitions. - -+Team Charlie Palette / Colors ownership: -+- Color management -+- API/database integration -+- Reusable color source of truth -+- Palette references for Sprites and Objects -+- Product Owner testable workflow -+ -+Team Charlie Objects ownership: -+- Object library -+- Object editor -+- Sprite assignment -+- Object properties -+- Collision configuration -+- Runtime object metadata -+- Object API/database contracts -+ - ## Team Delta - - - Engine -diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization.md ++ - Description: implement the Runtime Reliability Architecture covering resilient page loading, runtime availability events, Admin Logs, runtime logs, future telemetry, correlation IDs, dependency health, retry policies, duplicate suppression, notification routing, resolution lifecycle, diagnostic snapshots, privacy guardrails, and creator-facing runtime failure messaging. ++ - Remaining work: define event/API/database contracts, implement API-backed runtime availability records, add Admin Logs read model, add privacy-safe diagnostic snapshots, wire System Health aggregation, and add targeted validation. ++ - Blocking dependencies: PR_26179_001-runtime-reliability-architecture merged. ++ - Owning team: Team Charlie. ++ - Cross-team dependency: Team Delta owns future shared runtime/event hook implementation when engine/runtime/shared JS changes are required. + - [ ] Charlie - Palette / Colors + - Current completion percentage: 40%. + - Remaining work: color management, API/database integration, reusable color source of truth, Palette references for Sprites and Objects, and Product Owner testable workflow. +diff --git a/docs_build/dev/ProjectInstructions/standards/README.md b/docs_build/dev/ProjectInstructions/standards/README.md +index 0d34c10ac..a1a019189 100644 +--- a/docs_build/dev/ProjectInstructions/standards/README.md ++++ b/docs_build/dev/ProjectInstructions/standards/README.md +@@ -8,3 +8,7 @@ Rules: + - Generated validation evidence belongs under `docs_build/dev/reports/`. + - Historical reference material belongs under the root `archive/` tree. + - Reusable PR templates belong under `docs_build/dev/PR/templates/`. ++ ++## Active Architecture Standards ++ ++- Runtime Reliability Architecture: `docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md` +diff --git a/docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md b/docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md new file mode 100644 -index 000000000..a23272845 +index 000000000..348fe8a64 --- /dev/null -+++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization.md -@@ -0,0 +1,64 @@ -+# PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization ++++ b/docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md +@@ -0,0 +1,404 @@ ++# Runtime Reliability Architecture + -+Date: 2026-06-27 -+Team: OWNER -+Branch: PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization ++Status: Approved ++Owner: OWNER + +## Purpose + -+Finalize active Project Instructions cleanup, canonicalization, and backlog ownership governance. -+ -+## Scope -+ -+Documentation and governance only. -+ -+No runtime code, UI code, API code, database code, `start_of_day` files, history snapshots, or unrelated cleanup were changed. -+ -+## Changes -+ -+- Added a canonical governance owner map to the Project Instructions root. -+- Made overlap documents point to canonical owners instead of creating competing active rules: -+ - workflow and Product Owner testable completion: `pr_workflow.md` -+ - branch lifecycle and EOD main lock: `project_instructions_single_source_eod_lock.md` -+ - page-level Playwright: `test_structure_standardization.md` -+ - API/environment model: `environment_governance_model.md` -+ - environment configuration: `environment_configuration_standards.md` -+ - team backlog: `team_backlog_sod_eod_standard.md` -+ - team ownership: `team_ownership.md` -+- Replaced active `Mr. Q` manual validation wording with Product Owner wording. -+- Expanded backlog item requirements with owning team. -+- Updated backlog percentage cadence to SOD, after every accepted PR, and EOD. -+- Confirmed the backlog drives the next logical PRs. -+- Updated active Team Charlie ownership for Runtime, System Health, Environment Management, Palette / Colors, Sprites, and Objects. -+- Added Charlie backlog status: Runtime 100%, System Health 100%, Environment Management 100%, Palette / Colors 40%, Sprites 5%, and Objects 0%. -+- Updated Palette / Colors remaining work: color management, API/database integration, reusable color source of truth, Palette references for Sprites and Objects, and Product Owner testable workflow. -+- Updated Sprites MVP scope to include canvas/grid editor, width/height controls, Palette/Colors-only color selection, pixel painting, save/load sprite grid data through API/database, Product Owner testable workflow, and remove Category from Sprites planning. -+- Added Objects scope for object library, object editor, Sprite assignment, object properties, collision configuration, runtime object metadata, Object API/database contracts, and Product Owner testable workflow. -+ -+## Validation -+ -+- PASS: documentation/governance-only changed-file check. -+- PASS: `git diff --check` -+- PASS: no runtime files changed. -+- PASS: no UI files changed. -+- PASS: no API files changed. -+- PASS: no database files changed. -+- PASS: no `start_of_day` files changed. -+- PASS: no active `Mr. Q` manual validation wording remains. -+- PASS: no OWNER-only branch workflow wording remains. -+- PASS: active `Alpha` references are limited to the preserved non-team cancellation phrase. -+- PASS: canonical owner references exist. -+- PASS: Product Owner testable canonical owner remains `pr_workflow.md`. -+- PASS: page-level Playwright canonical owner remains `test_structure_standardization.md`. -+- PASS: API/environment canonical owner remains `environment_governance_model.md`. -+- PASS: branch lifecycle canonical owner remains `project_instructions_single_source_eod_lock.md`. -+- PASS: Team Charlie owns Palette / Colors, Sprites, and Objects. -+- PASS: repo-structured ZIP produced for documentation-only changes. -+ -+## Artifact -+ -+- `tmp/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_delta.zip` -+ -+## Next Logical PRs -+ -+No additional Project Instructions cleanup PR is required from this pass. Future cleanup should wait until after the OWNER governance stack is reviewed, unless the Product Owner identifies a new conflict. -diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_branch-validation.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_branch-validation.md -new file mode 100644 -index 000000000..995e565ba ---- /dev/null -+++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_branch-validation.md -@@ -0,0 +1,23 @@ -+# PR_26177_OWNER_012 Branch Validation ++Define the architecture standard for runtime reliability, runtime availability events, admin logs, runtime logs, future telemetry, and creator-facing failure behavior. + -+Date: 2026-06-27 -+Team: OWNER -+Branch: PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization ++This document is documentation/governance only. It does not implement runtime code, API routes, database schema, browser storage, notification delivery, UI changes, or telemetry providers. + -+## Result ++## Runtime Reliability Overview + -+PASS ++Runtime Reliability is the operational architecture for detecting, classifying, recording, routing, and resolving runtime failures without turning transient runtime state into product data. + -+## Checks ++Runtime Reliability covers: + -+- PASS: Work was performed on the active OWNER PR branch, not `main`. -+- PASS: Branch is stacked on `PR_26177_OWNER_011-codex-zip-and-next-pr-standard`. -+- PASS: Changes are limited to active Project Instructions and generated reports. -+- PASS: No runtime, UI, API, database, or `start_of_day` files changed. -+- PASS: `git diff --check` passed before report generation. -+- PASS: Required report files were generated. -+- PASS: Repo-structured ZIP artifact path is defined under `tmp/`. ++- page and tool loading failures ++- dependency availability failures ++- runtime availability events ++- admin-readable operational logs ++- runtime diagnostic logs ++- future telemetry and observability integrations ++- creator-facing failure messages + -+## Notes ++Runtime Reliability does not own: + -+This PR remains in the OWNER workstream and must not be merged to `main` until EOD closeout or explicit OWNER approval. -diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_manual-validation-notes.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_manual-validation-notes.md -new file mode 100644 -index 000000000..7de18e4a0 ---- /dev/null -+++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_manual-validation-notes.md -@@ -0,0 +1,24 @@ -+# PR_26177_OWNER_012 Manual Validation Notes ++- business events ++- audit events ++- user analytics ++- tool state payloads ++- project records ++- saved product data ++- hidden browser-owned source-of-truth data + -+Date: 2026-06-27 -+Team: OWNER ++Authoritative runtime reliability records must follow the environment governance model: + -+## Manual Review ++```text ++Browser -> API -> Database ++``` + -+Review these files: ++Browser pages may collect transient runtime context and submit it through the API/service contract. Browser pages must not become the authoritative source of runtime reliability records. + -+- `docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md` -+- `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md` -+- `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` -+- `docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md` -+- `docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md` ++## Resilient Page Loading + -+Confirm the canonical governance owner map is clear and that overlap files point back to canonical owner documents. ++Every user-facing runtime page should have a resilient loading path: + -+Confirm Team Charlie owns Runtime, System Health, Environment Management, Palette / Colors, Sprites, and Objects with the requested completion percentages and remaining work. ++- initialize a page-load correlation ID before dependency calls begin ++- load required static assets deterministically ++- validate required runtime dependencies before enabling primary workflows ++- show a creator-facing loading, degraded, blocked, or retry state when needed ++- avoid blank pages and silent failures ++- provide a bounded retry for safe, idempotent dependency reads ++- stop retrying when failure is not recoverable or would duplicate writes ++- record a runtime availability event for blocked or degraded loading + -+Confirm active backlog wording uses Product Owner validation language and drives the next logical PRs. ++Resilient loading must distinguish: + -+## Expected Reviewer Outcome ++- blocking failures that prevent the page or primary workflow from running ++- non-blocking failures that degrade secondary features ++- recoverable failures that can retry safely ++- non-recoverable failures that require user or operator action + -+The Product Owner should be able to identify the canonical owner document for workflow, branch rules, Product Owner testable completion, Playwright organization, API/environment rules, team backlog, and team ownership without reading competing active rules. -diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_requirements-checklist.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_requirements-checklist.md -new file mode 100644 -index 000000000..c08a85d44 ---- /dev/null -+++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_requirements-checklist.md -@@ -0,0 +1,35 @@ -+# PR_26177_OWNER_012 Requirements Checklist ++## Runtime Availability Events + -+Date: 2026-06-27 -+Team: OWNER ++Runtime Availability Events are operational records that describe runtime availability, degradation, recovery, and dependency state. + -+## Requirement Results -+ -+- PASS: Documentation/governance only. -+- PASS: Active Project Instructions reviewed. -+- PASS: Active instruction files updated only. -+- PASS: Historical snapshots were not modified. -+- PASS: No runtime changes. -+- PASS: Canonical governance owner map added. -+- PASS: Duplicated active guidance was removed where safe. -+- PASS: Append-style overlap files now point to canonical owner documents. -+- PASS: Military team spelling retained: OWNER, ALFA, BRAVO, CHARLIE, DELTA. -+- PASS: No new Greek team spelling introduced. -+- PASS: Active `Mr. Q` validation wording replaced with Product Owner wording. -+- PASS: Backlog item fields include owning team. -+- PASS: Backlog percentages update at SOD, after every accepted PR, and at EOD. -+- PASS: Backlog is authoritative for determining the next logical PRs. -+- PASS: Team Charlie owns Runtime, System Health, Environment Management, Palette / Colors, Sprites, and Objects. -+- PASS: Charlie backlog status records Runtime 100%, System Health 100%, Environment Management 100%, Palette / Colors 40%, Sprites 5%, and Objects 0%. -+- PASS: Palette / Colors remaining work includes color management, API/database integration, reusable color source of truth, Palette references for Sprites and Objects, and Product Owner testable workflow. -+- PASS: Sprites remaining work includes canvas/grid editor, width/height controls, Palette/Colors-only color selection, pixel painting, save/load sprite grid data through API/database, Product Owner testable workflow, and remove Category from Sprites planning. -+- PASS: Objects scope includes object library, object editor, Sprite assignment, object properties, collision configuration, runtime object metadata, Object API/database contracts, and Product Owner testable workflow. -+- PASS: Existing SOD, active team branch, sequential PR, no-return-to-main, and EOD clean main sync workflow remains present. -+- PASS: Required reports were generated. -+- PASS: Repo-structured ZIP artifact will be generated under `tmp/`. -+ -+## Restrictions -+ -+- PASS: No commit was made to `main`. -+- PASS: No `start_of_day` folders changed. -+- PASS: No unrelated cleanup. -diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_validation-lane.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_validation-lane.md -new file mode 100644 -index 000000000..d8729578c ---- /dev/null -+++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_validation-lane.md -@@ -0,0 +1,51 @@ -+# PR_26177_OWNER_012 Validation Lane ++Minimum event shape for future implementation: + -+Date: 2026-06-27 -+Team: OWNER ++- `eventId` ++- `correlationId` ++- `environment` ++- `sourcePage` ++- `sourceTool` ++- `sourceModule` ++- `eventType` ++- `severity` ++- `recoverability` ++- `userImpact` ++- `healthState` ++- `dependency` ++- `message` ++- `occurredAt` ++- `firstSeenAt` ++- `lastSeenAt` ++- `duplicateCount` ++- `resolutionStatus` + -+## Commands ++Runtime Availability Events are not Audit Events. If an availability failure also requires an audit trail, a separate Audit Event must be emitted through the Audit Event Contract. + -+```powershell -+git diff --check -+``` ++## Admin Logs Architecture + -+Result: PASS ++Admin Logs are an operator-facing read model for runtime reliability records. + -+```powershell -+node -e "documentation/governance-only changed-file check" -+``` ++Admin Logs must: + -+Result: PASS ++- read from API/database-backed operational records ++- support filtering by environment, severity, health state, dependency, page, tool, and correlation ID ++- separate unresolved, monitoring, resolved, and closed items ++- show duplicate-suppression counts and first/last seen timestamps ++- link diagnostic snapshots only when snapshots are privacy-safe ++- avoid exposing secrets, tokens, credentials, auth session state, or protected user payloads + -+```powershell -+rg -n "Mr\\. Q|What can Mr\\. Q|What Mr\\. Q" docs_build/dev/ProjectInstructions -+``` ++Admin Logs must not: + -+Result: PASS, no active matches. ++- rely on browser storage as the source of truth ++- rely on page arrays, JSON source files, or `/tmp` files as authoritative data ++- mutate runtime behavior directly ++- replace System Health or Audit Event records ++- expose raw provider internals that belong behind service boundaries + -+```powershell -+rg -n "Work must be committed only to the active OWNER branch|PR branches/commits stay on the active OWNER branch|active OWNER branch|OWNER branches|OWNER branch" docs_build/dev/ProjectInstructions -+``` ++## Runtime Logs vs Business Events + -+Result: PASS, no active OWNER-only branch workflow wording. ++Runtime Logs are operational diagnostics. They explain runtime health, page loading, dependency failures, retries, recoveries, and technical context. + -+```powershell -+node -e "canonical owner, backlog, and Team Charlie ownership checks" -+``` ++Business Events describe product or user-domain actions such as project creation, publishing, marketplace actions, collaboration, moderation, or account actions. ++ ++Rules: ++ ++- Runtime Logs must not be used as product analytics. ++- Business Events must not be inferred from runtime diagnostic logs. ++- Audit-required business actions must use the Audit Event Contract. ++- Notifications must use the Notification Contract when user/admin delivery is required. ++- Runtime Logs may reference business object IDs only when needed for diagnosis and permitted by privacy rules. ++- Runtime Logs must avoid storing product payloads. ++ ++## Future Telemetry Architecture ++ ++Future telemetry must be layered behind the runtime reliability API/service contract. ++ ++Telemetry phases: ++ ++1. Runtime Availability Event contract and persistence. ++2. Admin Logs read model. ++3. System Health aggregation. ++4. Diagnostic snapshot collection. ++5. Notification routing for operational alerts. ++6. External observability provider export. ++7. Trend analysis, charts, and reliability service-level indicators. ++ ++Telemetry exports must be optional and environment-managed. The deployable artifact must remain identical across environments; only `.env` or environment-managed secret/configuration values may differ. ++ ++## Severity Classifications ++ ++Runtime reliability severity is operational severity. It is separate from Audit Event severity. ++ ++Allowed runtime severity levels: ++ ++- `debug`: troubleshooting detail that does not indicate a failure. ++- `info`: normal operational state or successful recovery. ++- `warning`: degraded behavior or recoverable failure. ++- `error`: failed runtime behavior requiring attention or visible degradation. ++- `critical`: primary workflow unavailable or broad runtime outage. ++- `security`: suspected security, authorization, secret, or policy issue. ++ ++Severity must be assigned from observable impact, not from exception text alone. ++ ++## Recoverability Classifications ++ ++Allowed recoverability classifications: ++ ++- `autoRecovered`: the runtime recovered without user or operator action. ++- `retryable`: retry may succeed and is safe for the affected operation. ++- `userActionRequired`: the user can resolve the condition, such as reconnecting or signing in. ++- `operatorActionRequired`: an admin/operator must resolve dependency, configuration, or data issues. ++- `nonRecoverable`: the operation cannot continue safely in the current session. ++ ++Recoverability determines retry behavior, creator-facing messaging, and notification routing. ++ ++## User Impact Classifications ++ ++Allowed user impact classifications: ++ ++- `none`: no visible user impact. ++- `minor`: secondary feature degraded; primary workflow still works. ++- `degraded`: primary workflow works with reduced capability. ++- `blocked`: primary workflow cannot continue. ++- `dataRisk`: unsaved work, persistence, or integrity may be affected. ++- `securityRisk`: security or authorization may be affected. ++ ++User impact must be visible in Admin Logs and must drive creator-facing messaging. ++ ++## Correlation IDs ++ ++Correlation IDs connect page-load events, API calls, dependency checks, runtime logs, diagnostic snapshots, and admin log entries. ++ ++Rules: ++ ++- Create a page-load correlation ID before dependency calls begin. ++- Propagate the correlation ID through API calls where supported. ++- Include the correlation ID in runtime availability events. ++- Include the correlation ID in diagnostic snapshots. ++- Show the correlation ID in creator-facing support text only when it helps support triage. ++- Do not encode secrets, user identifiers, project payloads, or environment secrets in correlation IDs. ++ ++## Dependency Model ++ ++Runtime reliability must classify dependencies before implementation. ++ ++Dependency categories: ++ ++- `staticAssets`: HTML, CSS, JavaScript, images, and manifest assets. ++- `auth`: Supabase Auth and session state. ++- `api`: shared API/service contract. ++- `database`: Postgres-backed persistence. ++- `storage`: Cloudflare R2-backed object storage. ++- `runtimeEngine`: engine/runtime modules. ++- `toolRuntime`: tool bootstrap and hosted tool context. ++- `externalProvider`: external service or provider integration. ++- `browserCapability`: browser APIs required for the current workflow. ++ ++Dependency records must identify whether the dependency is required, optional, degraded-capable, retryable, or environment-managed. ++ ++## Retry Policies ++ ++Retry must be bounded and safe. ++ ++Rules: ++ ++- Retry only idempotent reads or explicitly safe operations. ++- Use bounded exponential backoff with jitter for retryable dependency reads. ++- Stop retrying when the operation is non-recoverable. ++- Do not retry writes that could duplicate product data unless the API provides idempotency keys. ++- Do not hide persistent failures behind endless retries. ++- Emit one availability event for the failure group and update duplicate counts instead of logging each retry as a new incident. ++- Surface creator-facing retry controls only when the user can safely retry. ++ ++## Health States ++ ++Allowed health states: + -+Result: PASS ++- `healthy`: expected behavior is available. ++- `degraded`: feature is available with reduced capability. ++- `partialOutage`: one or more required dependencies are unavailable while other areas still work. ++- `unavailable`: primary workflow cannot run. ++- `maintenance`: planned operator action limits availability. ++- `unknown`: health cannot be determined. + -+## Targeted Results ++Health states must be derivable from runtime availability events and dependency state. + -+- PASS: canonical governance owner map exists. -+- PASS: Product Owner testable owner is canonicalized. -+- PASS: page-level Playwright owner is canonicalized. -+- PASS: API/environment owner is canonicalized. -+- PASS: branch lifecycle owner is canonicalized. -+- PASS: backlog includes owning team and next logical PR wording. -+- PASS: Team Charlie owns Palette / Colors, Sprites, and Objects. -+- PASS: no runtime files changed. ++## Duplicate Suppression + -+## Playwright ++Duplicate suppression prevents noisy repeated failures from flooding Admin Logs and notifications. ++ ++Rules: ++ ++- Compute a stable failure fingerprint from source, dependency, event type, severity, recoverability, and sanitized message category. ++- Group duplicates within a bounded time window. ++- Preserve `firstSeenAt`, `lastSeenAt`, and `duplicateCount`. ++- Preserve the latest safe diagnostic summary. ++- Escalate if severity or user impact increases. ++- Do not suppress distinct correlation IDs when they indicate separate user-impacting sessions that require triage. ++ ++## Notification Routing ++ ++Notification routing decides who receives operational alerts. ++ ++Default routes: ++ ++- `debug` and `info`: Admin Logs only. ++- `warning`: Admin Logs; System Health aggregation when repeated or dependency-wide. ++- `error`: Admin Logs and System Health; notify operators when unresolved or repeated. ++- `critical`: Admin Logs, System Health, and operator notification. ++- `security`: Admin Logs, security/audit review path, and operator notification. ++ ++Creator-facing notifications must be limited to actionable, user-safe information. They must not expose internal dependency names, stack traces, secrets, SQL errors, provider details, or protected operational internals. ++ ++## Resolution Lifecycle ++ ++Allowed resolution lifecycle states: ++ ++- `detected`: event captured and recorded. ++- `triaged`: owner, dependency, and impact classification reviewed. ++- `mitigated`: workaround or retry restored user workflow, but root cause may remain. ++- `monitoring`: recovery observed and duplicates monitored. ++- `resolved`: root cause or configuration issue resolved. ++- `closed`: no further action required and retention policy applies. ++ ++Resolution records should include: ++ ++- owner ++- status ++- resolution summary ++- mitigation summary ++- linked correlation IDs ++- linked diagnostic snapshots ++- timestamps for state changes ++ ++## Diagnostic Snapshots ++ ++Diagnostic snapshots are privacy-safe operational summaries captured for triage. ++ ++Allowed content: ++ ++- correlation ID ++- environment ++- page/tool/module identifiers ++- dependency status ++- sanitized error category ++- retry count ++- timing summary ++- health state ++- browser capability summary ++ ++Prohibited content: ++ ++- secrets, tokens, credentials, cookies, or auth provider session state ++- raw SQL, stack traces containing secrets, or provider internals ++- tool payloads, project records, product data, or user-generated content ++- file bytes or image data URLs ++- payment state or protected marketplace transaction details ++ ++Large snapshots may be stored in R2 only through server/API ownership with privacy-safe metadata in Postgres. ++ ++## Privacy Requirements ++ ++Runtime reliability records must follow privacy-by-default rules: ++ ++- collect the minimum data needed for diagnosis ++- sanitize messages before persistence ++- avoid user-generated payloads ++- avoid browser-owned product data ++- avoid secrets and credentials ++- use stable identifiers only when required for support or triage ++- enforce retention and deletion policy before external telemetry export ++- separate operational diagnostics from business analytics ++ ++## Creator-facing Messaging Guidelines ++ ++Creator-facing messaging should be calm, actionable, and safe. ++ ++Messages should: ++ ++- name what is affected in user terms ++- say whether the user can retry ++- preserve unsaved work where possible ++- provide a support-safe correlation ID when useful ++- avoid blame or internal provider details ++- avoid stack traces and implementation names ++- distinguish temporary degradation from blocked workflows ++ ++Example message patterns: ++ ++- "This tool could not finish loading. Try again, or contact support with reference {correlationId}." ++- "Some runtime services are delayed. You can keep editing, but saving may be unavailable until the connection recovers." ++- "This action is temporarily unavailable. Your current page remains open." ++ ++## Blocking vs Non-Blocking Failures ++ ++Blocking failures prevent the page or primary workflow from continuing safely. ++ ++Examples: ++ ++- authentication unavailable for a protected workflow ++- API unavailable for required product data ++- database write unavailable for a save operation ++- required runtime module failed to load ++- required project/tool state cannot be read ++ ++Non-blocking failures degrade secondary behavior while preserving the primary workflow. ++ ++Examples: ++ ++- optional preview unavailable ++- non-required telemetry export unavailable ++- delayed health aggregation ++- optional notification delivery failure ++- degraded chart or admin summary view ++ ++Blocking status must be visible to the creator. Non-blocking status may be visible through subtle degraded-state messaging and Admin Logs. ++ ++## Runtime Logging Lifecycle ++ ++Runtime logging lifecycle: ++ ++1. Capture transient browser/runtime context. ++2. Normalize into a safe runtime event envelope. ++3. Attach correlation ID and dependency classification. ++4. Classify severity, recoverability, user impact, and health state. ++5. Suppress duplicates. ++6. Submit through the API/service contract. ++7. Persist authoritative records in the database. ++8. Route to Admin Logs, System Health, notification queues, or future telemetry exporters. ++9. Resolve through the resolution lifecycle. ++10. Retain, archive, or delete according to privacy and operational retention rules. ++ ++Browser capture is transient. The database-backed record is authoritative. ++ ++## Future Observability Roadmap ++ ++Future implementation should proceed in small PRs: ++ ++1. Runtime Availability Event contract and validation. ++2. API/database persistence for availability events. ++3. Runtime page-load correlation ID standard. ++4. Resilient page loading hooks for selected high-value pages. ++5. Admin Logs read model. ++6. Duplicate suppression and resolution lifecycle. ++7. Diagnostic snapshot capture with privacy guardrails. ++8. System Health aggregation from runtime availability records. ++9. Notification routing for critical and security events. ++10. External telemetry exporter behind environment-managed configuration. ++ ++No future observability work may introduce browser-owned product data, mock repositories as completion state, or environment-specific runtime code. +diff --git a/docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md b/docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md +index 6341fdf34..9e32c5911 100644 +--- a/docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md ++++ b/docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md +@@ -33,7 +33,7 @@ If a team has no assignment, no active branch, and no active PR, it is inactive + | Team Charlie | none | none | none | Available | Active ownership lane | + | Team Delta | PR_26177_DELTA_056-shared-validation-assertions | PR_26177_DELTA_056-shared-validation-assertions | PR_26177_DELTA_056-shared-validation-assertions | Active | OWNER override approved: Continue Team Delta random utility stack with PR_26177_DELTA_056-shared-validation-assertions | + | Team Golf | none | none | none | Available | Replacement active ownership lane for retired Team Gamma | +-| Team OWNER | none | none | none | Available | Governance Phase 1 complete | ++| Team OWNER | PR_26179_001-runtime-reliability-architecture | PR_26179_001-runtime-reliability-architecture | PR_26179_001-runtime-reliability-architecture | Active | OWNER-assigned documentation/governance architecture PR | + + ## Current Active Ownership Lanes + +diff --git a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md +index e7826a808..2cee356ca 100644 +--- a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md ++++ b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md +@@ -15,7 +15,7 @@ This file records active assignments and registry state. Workflow summaries here + | Team Charlie | none | none | none | Available | + | Team Delta | PR_26177_DELTA_056-shared-validation-assertions | PR_26177_DELTA_056-shared-validation-assertions | PR_26177_DELTA_056-shared-validation-assertions | Active | + | Team Golf | none | none | none | Available | +-| Team OWNER | none | none | none | Available | ++| Team OWNER | PR_26179_001-runtime-reliability-architecture | PR_26179_001-runtime-reliability-architecture | PR_26179_001-runtime-reliability-architecture | Active | + + Rules: + - Registry is the authoritative active-work view. +@@ -100,11 +100,13 @@ OWNER decision: Replacement active ownership lane for retired Team Gamma. + + ## Team OWNER + +-Status: Available ++Status: Active + +-Active assignment: none. ++Active assignment: PR_26179_001-runtime-reliability-architecture. + +-Active branch: none. ++Active branch: PR_26179_001-runtime-reliability-architecture. ++ ++Active PR: PR_26179_001-runtime-reliability-architecture. + + ## Team Name Registry + +diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md +new file mode 100644 +index 000000000..4c9f6984e +--- /dev/null ++++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md +@@ -0,0 +1,34 @@ ++# PR_26179_001-runtime-reliability-architecture ++ ++Date: 2026-06-27 12:32:39 ++Team: OWNER ++Branch: PR_26179_001-runtime-reliability-architecture ++Base HEAD: 1642cfb041a55c70e7e6e9f661a43e916210fde8 ++Scope: Documentation/governance-only runtime reliability architecture ++Status: PASS ++ ++## Summary ++ ++- Added Runtime Reliability Architecture under ProjectInstructions standards. ++- Indexed the architecture document from the standards README. ++- Added a Team Charlie implementation backlog item with Team Delta dependency noted for future runtime/shared JS hooks. ++- Updated active OWNER planning records for this PR branch. ++- No runtime/product/API/database implementation changed. ++ ++## Deliverables ++ ++- docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md ++- docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md ++- docs_build/dev/ProjectInstructions/standards/README.md ++- docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md ++- docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md ++- docs_build/dev/reports/codex_review.diff ++- docs_build/dev/reports/codex_changed_files.txt ++- docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md ++- docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md ++- docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md ++- tmp/PR_26179_001-runtime-reliability-architecture_delta.zip ++ ++## Product Owner Review ++ ++This PR is documentation-only. The Product Owner can review the Runtime Reliability Architecture and the new backlog item for future implementation ownership. +diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_branch-validation.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_branch-validation.md +new file mode 100644 +index 000000000..3cac7dcc2 +--- /dev/null ++++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_branch-validation.md +@@ -0,0 +1,8 @@ ++# Branch Validation - PR_26179_001-runtime-reliability-architecture ++ ++Status: PASS ++ ++- PASS: Started from synchronized main before branch creation. ++- PASS: Current branch is PR_26179_001-runtime-reliability-architecture. ++- PASS: Branch is not main for implementation, validation, commit, and push. ++- PASS: Work remains tied to PR identity PR_26179_001-runtime-reliability-architecture. +diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_manual-validation-notes.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_manual-validation-notes.md +new file mode 100644 +index 000000000..723eabdd5 +--- /dev/null ++++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_manual-validation-notes.md +@@ -0,0 +1,8 @@ ++# Manual Validation Notes - PR_26179_001-runtime-reliability-architecture ++ ++Status: PASS ++ ++- Reviewed active ProjectInstructions before editing. ++- Confirmed ProjectInstructions standards is the appropriate active owner for the architecture document. ++- Confirmed Team Charlie is the implementation owner because Runtime, System Health, Environment Management, and Operations are Charlie-owned; Team Delta dependency is noted for future runtime/shared JS hooks. ++- Confirmed this PR does not implement runtime code, API routes, database schema, UI, browser storage, or telemetry providers. +diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md +new file mode 100644 +index 000000000..691ba880c +--- /dev/null ++++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md +@@ -0,0 +1,29 @@ ++# Requirement Checklist - PR_26179_001-runtime-reliability-architecture ++ ++Status: PASS ++ ++- PASS: Documentation only. ++- PASS: Runtime Reliability overview documented. ++- PASS: Resilient Page Loading documented. ++- PASS: Runtime Availability Events documented. ++- PASS: Admin Logs architecture documented. ++- PASS: Runtime Logs vs Business Events documented. ++- PASS: Future Telemetry architecture documented. ++- PASS: Severity classifications documented. ++- PASS: Recoverability classifications documented. ++- PASS: User impact classifications documented. ++- PASS: Correlation IDs documented. ++- PASS: Dependency model documented. ++- PASS: Retry policies documented. ++- PASS: Health states documented. ++- PASS: Duplicate suppression documented. ++- PASS: Notification routing documented. ++- PASS: Resolution lifecycle documented. ++- PASS: Diagnostic snapshots documented. ++- PASS: Privacy requirements documented. ++- PASS: Creator-facing messaging guidelines documented. ++- PASS: Blocking vs non-blocking failures documented. ++- PASS: Runtime logging lifecycle documented. ++- PASS: Future observability roadmap documented. ++- PASS: Backlog item created for implementation ownership. ++- PASS: No implementation changes. +diff --git a/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md +new file mode 100644 +index 000000000..2a03e96eb +--- /dev/null ++++ b/docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md +@@ -0,0 +1,22 @@ ++# Validation Report - PR_26179_001-runtime-reliability-architecture ++ ++Status: PASS ++ ++## Commands + -+Not impacted. This PR is documentation/governance only. ++- git branch --show-current ++- git status --short --branch --untracked-files=all ++- git rev-list --left-right --count main...origin/main before branch creation ++- Section scan for required Runtime Reliability Architecture topics ++- Changed path scope scan for documentation/governance-only files ++- git diff --check ++ ++## Results ++ ++- Branch: PR_26179_001-runtime-reliability-architecture ++- Required architecture topics present: 22/22 ++- Backlog implementation ownership item present: PASS ++- Non-doc/governance changed paths: 0 ++- start_of_day changed paths: 0 ++- Runtime/product/API/database files changed: 0 ++- Playwright: not run; no runtime files changed. diff --git a/docs_build/dev/reports/codex_changed_files.txt b/docs_build/dev/reports/codex_changed_files.txt -index 85d74e87a..4c7d9fba2 100644 +index 4c7d9fba2..4ebd2023e 100644 --- a/docs_build/dev/reports/codex_changed_files.txt +++ b/docs_build/dev/reports/codex_changed_files.txt -@@ -1,10 +1,22 @@ -+docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md -+docs_build/dev/ProjectInstructions/README.txt -+docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md -+docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md -+docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md - docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md -+docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md -+docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md -+docs_build/dev/ProjectInstructions/addendums/multi_team.md - docs_build/dev/ProjectInstructions/addendums/pr_workflow.md - docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md --docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard.md --docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_branch-validation.md --docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_manual-validation-notes.md --docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_requirements-checklist.md --docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_validation-lane.md -+docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md -+docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md -+docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md -+docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md -+docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization.md -+docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_branch-validation.md -+docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_manual-validation-notes.md -+docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_requirements-checklist.md -+docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_validation-lane.md - docs_build/dev/reports/codex_changed_files.txt - docs_build/dev/reports/codex_review.diff -diff --git a/docs_build/dev/reports/codex_review.diff b/docs_build/dev/reports/codex_review.diff -index 0ea4e6438..17dfb5afa 100644 ---- a/docs_build/dev/reports/codex_review.diff -+++ b/docs_build/dev/reports/codex_review.diff -@@ -1,154 +1,549 @@ -+diff --git a/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md b/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md -+index d6617c986..ffd6f2438 100644 -+--- a/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md -++++ b/docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md -+@@ -58,6 +58,20 @@ Existing Project Instructions outside `docs_build/dev/ProjectInstructions/` rema -+ -+ `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` defines required Start of Day team briefings, End of Day team summaries, active team backlog fields, completion percentage update points, backlog-driven next PR selection, and official military team-name spelling. -+ -++## Canonical Governance Owners -++ -++When active guidance overlaps, use these canonical owner documents: -++ -++- Workflow and Product Owner testable completion: `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md` -++- START / WORK / END lifecycle, branch gates, mandatory hard stops, and EOD main lock: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` -++- Page-level Playwright organization and completion coverage: `docs_build/dev/ProjectInstructions/addendums/test_structure_standardization.md` -++- API/environment model and `Browser -> API -> Database` rule: `docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md` -++- Environment variable, URL, R2 prefix, and feature flag configuration: `docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md` -++- Team backlog fields, completion percentages, and next logical PR ownership: `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` -++- Team ownership and assignment routing: `docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md` -++ -++Other active addendums may summarize these rules, but they must point back to the canonical owner document and must not create a competing active rule. -++ -+ ## Environment Governance -+ -+ `docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md` defines the official environment model, environment invariance rule, shared API/service contract rule, required Supabase/Postgres/R2 services, required R2 prefixes, and SQLite retired status. -+@@ -97,7 +111,7 @@ OWNER override wording: -+ `OWNER override approved: ` -+ -+ OWNER follows the same safety rules: -+-- One active Team OWNER branch at a time. -++- Team OWNER follows the same one-active-branch discipline as every team. -+ - One active OWNER assignment at a time. -+ - OWNER may override team locks, but may not silently delete, rewrite, or remove protected instructions. -+ - OWNER override must be explicitly documented. -+diff --git a/docs_build/dev/ProjectInstructions/README.txt b/docs_build/dev/ProjectInstructions/README.txt -+index 1b647c6fd..bbfff9812 100644 -+--- a/docs_build/dev/ProjectInstructions/README.txt -++++ b/docs_build/dev/ProjectInstructions/README.txt -+@@ -16,7 +16,7 @@ No direct commits to main: -+ Do not commit directly to main. Normal work must use PR branches, draft PRs, validation evidence, and owner-controlled merge approval. -+ -+ Branch lifecycle: -+-Every PR follows exactly three phases: START, WORK, END. The canonical lifecycle is `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -++The canonical START / WORK / END lifecycle is `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -+ -+ OWNER override rule: -+ An OWNER override must use this wording: -+diff --git a/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md b/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md -+index 5fe1c43e4..7f9bcad29 100644 -+--- a/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md -++++ b/docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md -+@@ -13,14 +13,7 @@ Use `docs_build/dev/ProjectInstructions/` as the only active Project Instruction -+ Read `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` before implementation. -+ -+ Branch Lifecycle (Canonical): -+-- Every PR follows exactly three phases: START, WORK, END. -+-- Follow `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -+-- START begins on synchronized `main` and creates the PR branch only after all gates pass. -+-- WORK remains on the PR branch. Never checkout `main`. -+-- END merges, returns to synchronized `main`, publishes branch, HEAD SHA, and date/time, then stops all work. -+-- No commits on `main`. -+-- No implementation on `main`. -+-- No validation on `main` except start validation. -++- Follow `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` for START / WORK / END lifecycle, branch gates, mandatory hard stops, and EOD main lock. -+ -+ ## Start Team Alfa -+ -+diff --git a/docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md b/docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md -+index 798bb2cba..a829b0a15 100644 -+--- a/docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md -++++ b/docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md -+@@ -7,6 +7,10 @@ Owner: OWNER -+ -+ Require Codex and teams to confirm branch context before changing files. -+ -++Canonical branch lifecycle reference: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -++ -++This file owns branch context confirmation and stop conditions; it must not create a competing START / WORK / END lifecycle rule. -++ -+ ## Session Start Context -+ -+ At the start of work, report or validate: -+diff --git a/docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md b/docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md -+index 6f797306d..1851906ab 100644 -+--- a/docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md -++++ b/docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md -+@@ -7,6 +7,10 @@ Owner: OWNER -+ -+ Keep active work attached to the correct assigned team, branch, and OWNER decision. -+ -++Canonical branch lifecycle reference: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -++ -++This file owns branch lock enforcement and OWNER override handling; it must not create a competing START / WORK / END lifecycle rule. -++ -+ ## Active Work Lock -+ -+ - Work must occur on the active team branch. -+@@ -39,21 +43,13 @@ Keep active work attached to the correct assigned team, branch, and OWNER decisi -+ -+ ## Branch Lifecycle (Canonical) -+ -+-Every PR follows exactly three phases: -++The canonical branch lifecycle lives in: -+ -+ ```text -+-START -+-WORK -+-END -++docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md -+ ``` -+ -+-The canonical lifecycle lives in `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -+- -+-Branch lock governance enforces: -+-- START on synchronized `main`. -+-- WORK only on the PR branch. -+-- END by merging, returning to synchronized `main`, publishing branch, HEAD SHA, and date/time, then stopping all work. -+-- Mandatory hard stops before commits on `main`, dirty branch creation, non-`0 0` main sync, baseline SHA mismatch, unvalidated merge, or new unrelated workstream before synchronized main return. -++Branch lock governance enforces ownership and branch-lock compliance with that canonical lifecycle. -+ -+ ## OWNER Override -+ - diff --git a/docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md b/docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md --index 1c3671363..17be32ada 100644 -+index 17be32ada..a382a65df 100644 - --- a/docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md - +++ b/docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md --@@ -6,20 +6,31 @@ Standardize Codex deliverables, completion reporting, and artifact generation. -- -- ## ZIP Artifact Requirement -- ---Every Codex task must produce a ZIP artifact. --+Every Codex execution must produce a repo-structured ZIP artifact and the required reports. -- ---Applies to: ---- Success ---- Failure ---- Stop Gate ---- Partial Completion ---- Review Deliverables ---- Governance Deliverables --+This applies regardless of result: --+ --+- success --+- completion --+- partial completion --+- hard stop --+- blocked --+- validation failure --+- new information discovered --+- no files changed --+- review deliverables --+- governance deliverables --+ --+No exceptions. -- -- Minimum ZIP contents: ---- summary.md --+ --+- changed or preserved repo files from the run, stored at repo-relative paths --+- required reports under `docs_build/dev/reports/` -- -- Optional: --+ --+- summary.md -- - changed-files.txt -- - findings.md -- - validation.txt --@@ -28,11 +39,16 @@ Optional: -- ## Completion Reporting -- -- Codex responses must include: --+ -- - ZIP filename -- - ZIP location --+- repo-structured ZIP path --+- reports --+- changed file list -- - PR number(s) -- - Merge commit(s) -- - Validation results --+- branch, worktree, and local/origin sync status when relevant -- -- ## Tool MVP PR Report Requirements -- --@@ -82,3 +98,5 @@ unless explicitly requested. -- ## No ZIP Means Incomplete -- -- A task is not considered complete until the ZIP artifact is generated and reported. --+ --+If execution stops before implementation, validation, or commit, the stop result must still include the repo-structured ZIP and reports that document the hard stop, blocker, validation failure, or no-change result. --diff --git a/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md b/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md --index 145d08536..bee8bdd75 100644 ----- a/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md --+++ b/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md --@@ -126,10 +126,11 @@ Closed gates: -- - If validation fails, stop and report. -- - If conflict occurs, stop and report. -- - If OWNER decision is required, stop and report. ---- Every completed Codex PR run must produce a repo-structured ZIP under `tmp/`. ---- The ZIP rule applies to implementation, audit, report-only, validation-only, governance, and cleanup PRs. --+- Every Codex execution must produce a repo-structured ZIP under `tmp/`. --+- The ZIP rule applies to implementation, audit, report-only, validation-only, governance, cleanup, hard-stop, blocked, validation-failure, partial-completion, new-information, and no-change runs. -- - The ZIP must include all changed or preserved repo files from the run and must not replace required reports under `docs_build/dev/reports/`. ---- If no repo files changed, Codex must still create a ZIP containing the PR report that proves the no-change result, unless the run hard-stopped before producing outputs. --+- If no repo files changed, Codex must still create a ZIP containing the report that proves the no-change, hard-stop, blocked, validation-failure, or partial-completion result. --+- No exceptions. -+@@ -55,7 +55,7 @@ Codex responses must include: -+ Every tool MVP PR report must include: -+ - Product Owner testable outcome -+ - What Playwright tests -+-- What Mr. Q should manually test -++- What the Product Owner should manually test -+ - Whether the PR is part of a stacked MVP sequence -+ - Previous PR dependency -+ - Next PR dependency -+@@ -63,7 +63,7 @@ Every tool MVP PR report must include: -+ The report must answer: - -- ## Batch Governance Mode -+ ```text -+-What can Mr. Q test after applying this ZIP? -++What can the Product Owner test after applying this ZIP? -+ ``` - --@@ -240,6 +241,35 @@ Stop only for: -- - Validation failure -- - OWNER decision -+ If a tool MVP PR has no Playwright lane, the report must state why and list the manual Product Owner validation instead. -+diff --git a/docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md b/docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md -+index c6d8f192c..daf35f1d3 100644 -+--- a/docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md -++++ b/docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md -+@@ -23,25 +23,13 @@ Codex must use this as the only active source of truth for: - --+## Completed PR ZIP Review And Next Logical PRs --+ --+Whenever the Product Owner provides a completed PR ZIP to ChatGPT, ChatGPT shall: --+ --+- review the completed work --+- identify completed scope --+- identify remaining scope --+- update the team backlog and completion percentages --+- determine the next logical PRs --+- recommend the execution order --+- generate each recommended PR with: --+ - PR summary --+ - Codex command --+ - commit comment --+ - Playwright scope --+ - manual validation steps -+ ## Branch Lifecycle Start Gate -+ -+-Every PR follows exactly three phases: -++Codex must follow the canonical lifecycle in: -+ -+ ```text -+-START -+-WORK -+-END -++docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md -+ ``` -+ -+-Codex must follow the canonical lifecycle in: -+- -+-`docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` -+- -+-Startup enforcement: -+-- START begins on synchronized `main`. -+-- WORK remains on the PR branch. Never checkout `main`. -+-- END merges, returns to synchronized `main`, publishes branch, HEAD SHA, and date/time, then stops all work. -+-- STOP if current branch is `main` before commit. -+-- STOP if attempting to push `main`. -+-- STOP if a new PR starts before returning to synchronized `main`. -++This startup addendum only requires Codex to read and apply that canonical lifecycle; it must not define a competing lifecycle rule. -+ -+ Deprecated Project Instructions material outside `docs_build/dev/ProjectInstructions/` is reference-only and must not override active governance. -+ -+diff --git a/docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md b/docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md -+index 5a91f904c..414bf9758 100644 -+--- a/docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md -++++ b/docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md -+@@ -11,6 +11,10 @@ This addendum is governance/documentation only. It does not change runtime behav -+ -+ ## Source Model -+ -++Canonical environment/API model reference: `docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md`. - + --+Use plural wording: `next logical PRs`. -++This file owns environment variable names, URL configuration, R2 prefix configuration, and feature flag configuration only. - + --+Unless blocked by dependencies or directed otherwise by the Product Owner, ChatGPT should generate enough sequential PRs to complete the current backlog item to a Product Owner testable state rather than stopping after a single PR. -+ This standard builds on: -+ -+ ```text -+@@ -88,12 +92,10 @@ R2 project, backup, export, import, or future storage paths must stay under the -+ -+ ## API/Service Contract Configuration -+ -+-One shared API/service contract is required across Local (VS Code), DEV, IST, UAT, and PROD. -++The canonical shared API/service contract rule lives in `docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md`. -+ -+-Rules: -++This section owns configuration-only API URL requirements: -+ -+-- Browser/UI/runtime code must follow `Browser -> API -> Database` for authoritative product data. -+-- `Local API` means the same shared API/service contract running locally, not a separate local-only API implementation. -+ - API URLs may differ by `.env` only. -+ - Do not split Local API and Public API contracts. -+ - Do not create environment-specific API/service contracts. -+diff --git a/docs_build/dev/ProjectInstructions/addendums/multi_team.md b/docs_build/dev/ProjectInstructions/addendums/multi_team.md -+index 7ba2cae8d..763dccc8a 100644 -+--- a/docs_build/dev/ProjectInstructions/addendums/multi_team.md -++++ b/docs_build/dev/ProjectInstructions/addendums/multi_team.md -+@@ -1,5 +1,11 @@ -+ # Multi-Team Codex Execution Governance -+ -++Canonical workflow reference: `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md`. - + --+The Product Owner should not have to ask: -++Canonical branch lifecycle reference: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. - + --+- `What is next?` --+- `Create the next PR.` --+- `Continue.` -++This file owns multi-team execution coordination and must not create competing workflow or branch lifecycle rules. - + --+The backlog drives the next recommended PRs automatically. -+ ## Four Active Delivery Teams -+ -+ The single authoritative four-team ownership definition is: -+@@ -65,7 +71,7 @@ Rules: -+ ## Day Work / EOD Merge Rule -+ -+ During active work: -+-- Work happens on assigned team branches, OWNER branches, or scoped PR branches. -++- Work happens on active non-main team branches or scoped PR branches. -+ - Commits are allowed only on assigned non-main branches. -+ - Pushes are allowed and expected. -+ - Draft PRs are allowed and expected. -+diff --git a/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md b/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md -+index bee8bdd75..97a73ca30 100644 -+--- a/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md -++++ b/docs_build/dev/ProjectInstructions/addendums/pr_workflow.md -+@@ -46,31 +46,11 @@ This section supersedes older active wording that implies returning to `main` be -+ -+ ## Branch Lifecycle (Canonical) -+ -+-Every PR follows exactly three phases: -+- -+-```text -+-START -+-WORK -+-END -+-``` -+- -+ The canonical START, WORK, END, Daily Synchronization, and Mandatory Hard Stops rules live in: -+ -+ `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` -+ -+-PR workflow must follow that lifecycle exactly. -+- -+-Summary: -+-- START happens on synchronized `main` only and creates the PR branch only after all required gates pass. -+-- WORK happens only on the PR branch. -+-- END validates, commits, pushes, opens/updates the PR, merges, returns to synchronized `main`, publishes branch, HEAD SHA, and date/time, then stops all work. -+-- No commits on `main`. -+-- No implementation on `main`. -+-- No validation on `main` except start validation. -+-- Never checkout `main` during WORK. -+-- STOP before commit if current branch is `main`. -+-- STOP if current branch changes unexpectedly. -+-- STOP if attempting to push `main`. -++PR workflow must follow that lifecycle exactly and must not create a competing lifecycle rule. -+ -+ ## PR Lifecycle States -+ -+@@ -153,7 +133,7 @@ Do not stop after every small PR unless blocked by branch state, failed validati -+ Each tool MVP PR plan or template must include: -+ - Product Owner testable outcome -+ - What Playwright tests -+-- What Mr. Q should manually test -++- What the Product Owner should manually test -+ - Whether the PR is part of a stacked MVP sequence -+ - Previous PR dependency -+ - Next PR dependency -+@@ -162,6 +142,8 @@ Visible acceptance must be Creator-facing first. Architecture can be handled und -+ -+ ## Product Owner Testable Definition -+ -++Canonical owner: this section is the active canonical Product Owner testable completion rule. - + -- ## EOD Main Lock -+ A request to complete a page, tool, MVP, or testable experience means Product Owner testable by default. Codex must deliver a working Product Owner testable feature, not a shell or foundation page, unless the Product Owner explicitly requests a shell/foundation PR. - -- End of Day: -+ A Product Owner testable outcome means the Product Owner can: - diff --git a/docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md b/docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md --index 437c01800..be3555469 100644 -+index be3555469..e6d6c7ce8 100644 - --- a/docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md - +++ b/docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md --@@ -53,6 +53,8 @@ The backlog is the authoritative source for determining the next PRs. -+@@ -42,14 +42,15 @@ Each backlog item must track: -+ - current completion percentage -+ - remaining work -+ - blocking dependencies -++- owning team -+ -+ Completion percentages are updated: -+ -+ - at SOD -+-- after each accepted PR -++- after every accepted PR -+ - at EOD -+ -+-The backlog is the authoritative source for determining the next PRs. -++The backlog is the authoritative source for determining the next logical PRs. - - If the backlog and a generated report conflict, the backlog wins unless OWNER explicitly approves a newer governance decision. - --+When the Product Owner provides a completed PR ZIP, ChatGPT must review that ZIP, update the active team backlog and completion percentages, and recommend the next logical PRs needed to keep moving toward a Product Owner testable outcome. -+diff --git a/docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md b/docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md -+index 2bcc52a60..5da2f9952 100644 -+--- a/docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md -++++ b/docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md -+@@ -24,7 +24,7 @@ One large Codex command -> multiple focused stacked PRs -> each PR has a Product -+ - Each PR must answer: -+ -+ ```text -+-What can Mr. Q test after applying this ZIP? -++What can the Product Owner test after applying this ZIP? -+ ``` -+ -+ - Codex must continue through the stacked PR sequence unless blocked by: -+@@ -40,45 +40,14 @@ For tool MVP PR planning, visible acceptance must be Creator-facing first. -+ -+ Architecture can be handled under the covers, but PR purpose must be user-testable. -+ -+-A request to complete a page, tool, MVP, or testable experience means Product Owner testable by default. Codex must deliver a working Product Owner testable feature, not a shell or foundation page, unless the Product Owner explicitly requests a shell/foundation PR. -+- -+-A Product Owner testable outcome means the Product Owner can: -+- -+-- open the page/tool -+-- perform the primary workflow -+-- save/load data where applicable -+-- observe expected results -+-- validate success and failure states -+-- follow manual validation steps from the PR report -+- -+-Not acceptable as complete/testable: -+- -+-- shell-only page -+-- route-only page -+-- navigation-only PR -+-- template-only page -+-- placeholder controls -+-- static table with no workflow -+-- `Not implemented yet` -+-- `coming soon` -+-- placeholder-only workspace, inspector, or output sections -+-- planned-only tile -+-- route that loads but cannot be used -+- -+-Required for Product Owner testable completion: -+- -+-- visible working controls -+-- API-backed data where required -+-- validation and error states -+-- empty states -+-- save/load behavior where applicable -+-- manual validation steps for Product Owner -+-- targeted Playwright coverage where impacted. -++Canonical reference: `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md` owns the Product Owner testable definition and no-shell completion rule. -++ -++Canonical Playwright reference: `docs_build/dev/ProjectInstructions/addendums/test_structure_standardization.md` owns page-level Playwright organization and minimum completion coverage. -+ -+ Each tool MVP PR must state: -+ - Product Owner testable outcome -+ - What Playwright tests -+-- What Mr. Q should manually test -++- What the Product Owner should manually test -+ - Whether the PR is part of a stacked MVP sequence -+ - Previous PR dependency -+ - Next PR dependency -+diff --git a/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md b/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md -+index cc9ddc88c..c0e3336a9 100644 -+--- a/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md -++++ b/docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md -+@@ -2,19 +2,22 @@ -+ -+ ## Backlog Item Tracking Standard -+ -++Canonical backlog tracking owner: `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md`. - + -- ## Start Of Day Team Briefing -+ Every active team owns an active backlog when it has assigned work. - -- When a team is assigned, ChatGPT/Codex must provide this briefing before implementation begins: --diff --git a/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard.md b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard.md -+-Each backlog item must track: -++Backlog entries in this file follow the canonical field list, including: -+ -+ - Name -+ - Description -+ - Current completion percentage -+ - Remaining work -+ - Blocking dependencies -++- Owning team -+ -+-Completion percentages are updated at SOD, after each accepted PR, and at EOD. -++Completion percentages are updated at SOD, after every accepted PR, and at EOD. -+ -+-The backlog is the authoritative source for determining the next PRs. -++The backlog is the authoritative source for determining the next logical PRs. -+ -+ ## Game Journey MVP -+ -+@@ -44,7 +47,7 @@ The backlog is the authoritative source for determining the next PRs. -+ - [ ] Bravo - Asset Studio V2 -+ - [ ] Charlie - Sprites canvas editor MVP -+ - Sprites is a creator tool, not only an asset metadata library. -+- - MVP requires canvas/grid editor behavior, width/height controls, Palette/Colors-only reusable colors, color selection from Palette/Colors, pixel painting, save/load sprite grid data through the API/database, and Product Owner manual validation. -++ - MVP requires canvas/grid editor behavior, width/height controls, Palette/Colors references only, pixel painting, save/load sprite grid data through the API/database, and a Product Owner testable workflow. -+ - Category is removed from Sprites MVP planning. -+ - [ ] Bravo - Animation Studio V2 -+ - [ ] Bravo - Palette Manager -+@@ -65,7 +68,8 @@ The backlog is the authoritative source for determining the next PRs. -+ -+ 0% Complete — Create the things players interact with -+ -+-- [ ] Alfa - Objects -++- [ ] Charlie - Objects -++ - Objects includes object library, object editor, Sprite assignment, object properties, collision configuration, runtime object metadata, and Object API/database contracts. -+ - [ ] Alfa - Characters -+ - [ ] Alfa - Object Behaviors -+ -+@@ -226,6 +230,7 @@ Current OWNER clarification: -+ -+ ### Team Charlie -+ -++- Active ownership: Runtime, System Health, Environment Management, Sprites, Objects. -+ - [ ] Charlie - Guardrail hardening -+ - [ ] Charlie - Browser validation hardening -+ - [ ] Charlie - Remaining test relocation audit -+@@ -257,6 +262,10 @@ Current OWNER clarification: -+ - observability integrations -+ - [ ] Charlie - Infrastructure dashboard -+ - [ ] Charlie - Environment validation -++- [ ] Charlie - Sprites canvas editor MVP -++ - Scope: canvas/grid editor, width/height controls, Palette/Colors references only, pixel painting, save/load sprite grid data, and Product Owner testable workflow. -++- [ ] Charlie - Objects -++ - Scope: object library, object editor, Sprite assignment, object properties, collision configuration, runtime object metadata, and Object API/database contracts. -+ -+ ### Team Delta -+ -+diff --git a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md -+index 4253971d9..e7826a808 100644 -+--- a/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md -++++ b/docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md -+@@ -1,5 +1,11 @@ -+ # TEAM_ASSIGNMENTS -+ -++Canonical workflow reference: `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md`. -++ -++Canonical branch lifecycle reference: `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -++ -++This file records active assignments and registry state. Workflow summaries here are subordinate to the canonical workflow and branch lifecycle documents. -++ -+ # Active Team Registry -+ -+ | Team | Assignment | Branch | PR | Status | -+@@ -197,7 +203,7 @@ Conflict note: -+ ## Day Work / EOD Merge Rule -+ -+ During active work: -+-- Work happens on assigned team branches, OWNER branches, or scoped PR branches. -++- Work happens on active non-main team branches or scoped PR branches. -+ - Commits are allowed only on assigned non-main branches. -+ - Pushes are allowed and expected. -+ - Draft PRs are allowed and expected. -+@@ -263,23 +269,10 @@ Teams must use only `docs_build/dev/ProjectInstructions/` as the active Project -+ -+ ## Branch Lifecycle (Canonical) -+ -+-Every PR follows exactly three phases: -++Teams must follow the canonical branch lifecycle in: -+ -+ ```text -+-START -+-WORK -+-END -++docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md -+ ``` -+ -+-Teams must follow `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`. -+- -+-Assignment governance enforces: -+-- START begins on synchronized `main`. -+-- WORK remains on the PR branch. Never checkout `main`. -+-- END merges, returns to synchronized `main`, publishes branch, HEAD SHA, and date/time, then stops all work. -+-- No commits on `main`. -+-- No implementation on `main`. -+-- No validation on `main` except start validation. -+-- STOP if current branch is `main` before commit. -+-- STOP if attempting to push `main`. -+-- STOP if new PR work starts before returning to synchronized `main`. -++Assignment governance records active team and branch state; it must not create a competing lifecycle rule. -+diff --git a/docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md b/docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md -+index 30b4f2dfe..fb8497c1f 100644 -+--- a/docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md -++++ b/docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md -+@@ -30,11 +30,13 @@ This section is the current OWNER-approved active ownership alignment. -+ - Repository compliance -+ - Validation -+ - Infrastructure -++- Runtime -+ - Storage -+-- Environment management -++- Environment Management -+ - System Health -+ - Operations -+ - Sprites canvas editor MVP -++- Objects -+ -+ Team Charlie System Health owns: -+ - Environment Summary -+@@ -45,9 +47,18 @@ Team Charlie System Health owns: -+ -+ Team Charlie Sprites ownership: -+ - Sprites is a creator tool, not only an asset metadata library. -+-- Sprites MVP requires canvas/grid editor behavior, width/height controls, Palette/Colors-only reusable colors, color selection from Palette/Colors, pixel painting, save/load sprite grid data through the API/database, and Product Owner manual validation. -++- Sprites MVP requires canvas/grid editor behavior, width/height controls, Palette/Colors references only, pixel painting, save/load sprite grid data through the API/database, and a Product Owner testable workflow. -+ - Sprites must not own reusable color definitions. -+ -++Team Charlie Objects ownership: -++- Object library -++- Object editor -++- Sprite assignment -++- Object properties -++- Collision configuration -++- Runtime object metadata -++- Object API/database contracts -++ -+ ## Team Delta -+ -+ - Engine -+diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization.md - new file mode 100644 --index 000000000..bc4213d30 -+index 000000000..cbbefda41 - --- /dev/null --+++ b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard.md --@@ -0,0 +1,56 @@ --+# PR_26177_OWNER_011-codex-zip-and-next-pr-standard -++++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization.md -+@@ -0,0 +1,62 @@ -++# PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization - + - +Date: 2026-06-27 - +Team: OWNER --+Branch: PR_26177_OWNER_011-codex-zip-and-next-pr-standard -++Branch: PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization - + - +## Purpose - + --+Add governance that every Codex execution produces reports and a repo-structured ZIP, and that completed PR ZIP review automatically drives the next logical PRs. -++Finalize active Project Instructions cleanup, canonicalization, and backlog ownership governance. - + - +## Scope - + -@@ -158,55 +553,61 @@ index 000000000..bc4213d30 - + - +## Changes - + --+- Strengthened the Codex artifact standard so every Codex execution produces required reports and a repo-structured ZIP. --+- Made the ZIP/report rule apply to success, completion, partial completion, hard stop, blocked, validation failure, new information, no-change, review, and governance results. --+- Removed the previous exception that allowed hard stops before outputs to skip ZIP/report delivery. --+- Required Codex responses to return ZIP path, reports, changed file list, validation results, and branch/worktree/sync status when relevant. --+- Added completed PR ZIP review governance: --+ - review completed work --+ - identify completed and remaining scope --+ - update team backlog and completion percentages --+ - determine the next logical PRs --+ - recommend execution order --+ - generate each recommended PR with summary, Codex command, commit comment, Playwright scope, and manual validation steps --+- Confirmed the backlog drives next recommended PRs automatically. --+- Preserved the existing SOD, active team branch, sequential workstream, EOD, Product Owner testable, and page-level Playwright workflow rules. -++- Added a canonical governance owner map to the Project Instructions root. -++- Made overlap documents point to canonical owners instead of creating competing active rules: -++ - workflow and Product Owner testable completion: `pr_workflow.md` -++ - branch lifecycle and EOD main lock: `project_instructions_single_source_eod_lock.md` -++ - page-level Playwright: `test_structure_standardization.md` -++ - API/environment model: `environment_governance_model.md` -++ - environment configuration: `environment_configuration_standards.md` -++ - team backlog: `team_backlog_sod_eod_standard.md` -++ - team ownership: `team_ownership.md` -++- Replaced active `Mr. Q` manual validation wording with Product Owner wording. -++- Expanded backlog item requirements with owning team. -++- Updated backlog percentage cadence to SOD, after every accepted PR, and EOD. -++- Confirmed the backlog drives the next logical PRs. -++- Updated active Team Charlie ownership for Runtime, System Health, Environment Management, Sprites, and Objects. -++- Updated Sprites MVP scope to include canvas/grid editor, width/height controls, Palette/Colors references only, pixel painting, save/load sprite grid data, and Product Owner testable workflow. -++- Added Objects scope for object library, object editor, Sprite assignment, object properties, collision configuration, runtime object metadata, and Object API/database contracts. - + - +## Validation - + --+- PASS: `git diff --cached --check -- . :(exclude)docs_build/dev/reports/codex_review.diff` - +- PASS: documentation/governance-only changed-file check. --+- PASS: ZIP-on-every-result rule exists. --+- PASS: hard stops require ZIP/report output. --+- PASS: `next logical PRs` plural wording exists. --+- PASS: automatic next PR planning is tied to completed PR ZIP review. --+- PASS: SOD starts from latest synchronized `main`. --+- PASS: SOD creates or uses the active team branch. --+- PASS: all commits go to the active team branch, not `main`. --+- PASS: sequential PRs stay on the active team branch/workstream during the day. --+- PASS: EOD returns to `main` and verifies clean sync `0 0`. --+- PASS: Product Owner testable completion rule remains present. --+- PASS: page-level Playwright completion gate remains present. -++- PASS: `git diff --check` - +- PASS: no runtime files changed. -++- PASS: no UI files changed. -++- PASS: no API files changed. -++- PASS: no database files changed. -++- PASS: no `start_of_day` files changed. -++- PASS: no active `Mr. Q` manual validation wording remains. -++- PASS: no OWNER-only branch workflow wording remains. -++- PASS: active `Alpha` references are limited to the preserved non-team cancellation phrase. -++- PASS: canonical owner references exist. -++- PASS: Product Owner testable canonical owner remains `pr_workflow.md`. -++- PASS: page-level Playwright canonical owner remains `test_structure_standardization.md`. -++- PASS: API/environment canonical owner remains `environment_governance_model.md`. -++- PASS: branch lifecycle canonical owner remains `project_instructions_single_source_eod_lock.md`. -++- PASS: Team Charlie owns both Sprites and Objects. -++- PASS: repo-structured ZIP produced for documentation-only changes. - + - +## Artifact - + --+- `tmp/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_delta.zip` -++- `tmp/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_delta.zip` - + --+## Manual Validation Notes -++## Next Logical PRs - + --+Reviewers should confirm the active governance now makes ZIP/report delivery mandatory for every Codex result and makes completed PR ZIP review produce the next logical PRs without requiring the Product Owner to ask for continuation. --diff --git a/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_branch-validation.md b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_branch-validation.md -++No additional Project Instructions cleanup PR is required from this pass. Future cleanup should wait until after the OWNER governance stack is reviewed, unless the Product Owner identifies a new conflict. -+diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_branch-validation.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_branch-validation.md - new file mode 100644 --index 000000000..cd2754f9f -+index 000000000..995e565ba - --- /dev/null --+++ b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_branch-validation.md -++++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_branch-validation.md - @@ -0,0 +1,23 @@ --+# PR_26177_OWNER_011 Branch Validation -++# PR_26177_OWNER_012 Branch Validation - + - +Date: 2026-06-27 - +Team: OWNER --+Branch: PR_26177_OWNER_011-codex-zip-and-next-pr-standard -++Branch: PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization - + - +## Result - + -@@ -215,23 +616,23 @@ index 000000000..cd2754f9f - +## Checks - + - +- PASS: Work was performed on the active OWNER PR branch, not `main`. --+- PASS: Branch is stacked on `PR_26177_OWNER_010-team-backlog-sod-eod-standard`. -++- PASS: Branch is stacked on `PR_26177_OWNER_011-codex-zip-and-next-pr-standard`. - +- PASS: Changes are limited to active Project Instructions and generated reports. - +- PASS: No runtime, UI, API, database, or `start_of_day` files changed. --+- PASS: Staged whitespace validation passed with generated `codex_review.diff` excluded. -++- PASS: `git diff --check` passed before report generation. - +- PASS: Required report files were generated. - +- PASS: Repo-structured ZIP artifact path is defined under `tmp/`. - + - +## Notes - + - +This PR remains in the OWNER workstream and must not be merged to `main` until EOD closeout or explicit OWNER approval. --diff --git a/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_manual-validation-notes.md b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_manual-validation-notes.md -+diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_manual-validation-notes.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_manual-validation-notes.md - new file mode 100644 --index 000000000..af329a4cb -+index 000000000..2b111a71f - --- /dev/null --+++ b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_manual-validation-notes.md --@@ -0,0 +1,20 @@ --+# PR_26177_OWNER_011 Manual Validation Notes -++++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_manual-validation-notes.md -+@@ -0,0 +1,24 @@ -++# PR_26177_OWNER_012 Manual Validation Notes - + - +Date: 2026-06-27 - +Team: OWNER -@@ -240,24 +641,28 @@ index 000000000..af329a4cb - + - +Review these files: - + --+- `docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md` -++- `docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md` - +- `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md` - +- `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` -++- `docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md` -++- `docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md` -++ -++Confirm the canonical governance owner map is clear and that overlap files point back to canonical owner documents. - + --+Confirm they require every Codex result to include reports and a repo-structured ZIP, including hard stops and no-change results. -++Confirm Team Charlie owns Runtime, System Health, Environment Management, Sprites, and Objects. - + --+Confirm completed PR ZIP review now drives the next logical PRs and produces enough sequential PRs to reach a Product Owner testable outcome unless blocked or directed otherwise. -++Confirm active backlog wording uses Product Owner validation language and drives the next logical PRs. - + - +## Expected Reviewer Outcome - + --+The Product Owner should no longer need to ask for continuation after handing ChatGPT a completed PR ZIP; the backlog and ZIP review should automatically drive the next recommended PRs. --diff --git a/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_requirements-checklist.md b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_requirements-checklist.md -++The Product Owner should be able to identify the canonical owner document for workflow, branch rules, Product Owner testable completion, Playwright organization, API/environment rules, team backlog, and team ownership without reading competing active rules. -+diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_requirements-checklist.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_requirements-checklist.md - new file mode 100644 --index 000000000..0dc03d042 -+index 000000000..d9a12c54e - --- /dev/null --+++ b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_requirements-checklist.md --@@ -0,0 +1,30 @@ --+# PR_26177_OWNER_011 Requirements Checklist -++++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_requirements-checklist.md -+@@ -0,0 +1,33 @@ -++# PR_26177_OWNER_012 Requirements Checklist - + - +Date: 2026-06-27 - +Team: OWNER -@@ -265,20 +670,23 @@ index 000000000..0dc03d042 - +## Requirement Results - + - +- PASS: Documentation/governance only. --+- PASS: Active Project Instructions reviewed and updated. -++- PASS: Active Project Instructions reviewed. - +- PASS: Active instruction files updated only. --+- PASS: Historical snapshots were not rewritten. -++- PASS: Historical snapshots were not modified. - +- PASS: No runtime changes. --+- PASS: ZIP-on-every-result governance added. --+- PASS: Rule applies to success, completion, partial completion, hard stop, blocked, validation failure, new information, and no files changed. --+- PASS: Every Codex execution must return repo-structured ZIP path, reports, changed file list, validation results, and branch/worktree/sync status when relevant. --+- PASS: `No exceptions` wording added. --+- PASS: Automatic next PR planning tied to Product Owner completed PR ZIP review. --+- PASS: `next logical PRs` plural wording exists. --+- PASS: Recommended PR output includes PR summary, Codex command, commit comment, Playwright scope, and manual validation steps. --+- PASS: Product Owner should not need to ask `What is next?`, `Create the next PR.`, or `Continue.` --+- PASS: Backlog drives next recommended PRs automatically. --+- PASS: Existing SOD/main, active team branch, stacked PR, EOD, Product Owner testable, and page-level Playwright rules remain present. -++- PASS: Canonical governance owner map added. -++- PASS: Duplicated active guidance was removed where safe. -++- PASS: Append-style overlap files now point to canonical owner documents. -++- PASS: Military team spelling retained: OWNER, ALFA, BRAVO, CHARLIE, DELTA. -++- PASS: No new Greek team spelling introduced. -++- PASS: Active `Mr. Q` validation wording replaced with Product Owner wording. -++- PASS: Backlog item fields include owning team. -++- PASS: Backlog percentages update at SOD, after every accepted PR, and at EOD. -++- PASS: Backlog is authoritative for determining the next logical PRs. -++- PASS: Team Charlie owns Runtime, System Health, Environment Management, Sprites, and Objects. -++- PASS: Sprites MVP scope includes canvas/grid editor, width/height controls, Palette/Colors references only, pixel painting, save/load sprite grid data, and Product Owner testable workflow. -++- PASS: Objects scope includes object library, object editor, Sprite assignment, object properties, collision configuration, runtime object metadata, and Object API/database contracts. -++- PASS: Existing SOD, active team branch, sequential PR, no-return-to-main, and EOD clean main sync workflow remains present. - +- PASS: Required reports were generated. - +- PASS: Repo-structured ZIP artifact will be generated under `tmp/`. - + -@@ -287,13 +695,13 @@ index 000000000..0dc03d042 - +- PASS: No commit was made to `main`. - +- PASS: No `start_of_day` folders changed. - +- PASS: No unrelated cleanup. --diff --git a/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_validation-lane.md b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_validation-lane.md -+diff --git a/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_validation-lane.md b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_validation-lane.md - new file mode 100644 --index 000000000..0eae5bc5a -+index 000000000..1f8990d29 - --- /dev/null --+++ b/docs_build/dev/reports/PR_26177_OWNER_011-codex-zip-and-next-pr-standard_validation-lane.md --@@ -0,0 +1,43 @@ --+# PR_26177_OWNER_011 Validation Lane -++++ b/docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_validation-lane.md -+@@ -0,0 +1,51 @@ -++# PR_26177_OWNER_012 Validation Lane - + - +Date: 2026-06-27 - +Team: OWNER -@@ -301,7 +709,7 @@ index 000000000..0eae5bc5a - +## Commands - + - +```powershell --+git diff --cached --check -- . ":(exclude)docs_build/dev/reports/codex_review.diff" -++git diff --check - +``` - + - +Result: PASS -@@ -313,25 +721,33 @@ index 000000000..0eae5bc5a - +Result: PASS - + - +```powershell --+node -e "required ZIP, next logical PRs, workflow preservation checks" -++rg -n "Mr\\. Q|What can Mr\\. Q|What Mr\\. Q" docs_build/dev/ProjectInstructions -++``` -++ -++Result: PASS, no active matches. -++ -++```powershell -++rg -n "Work must be committed only to the active OWNER branch|PR branches/commits stay on the active OWNER branch|active OWNER branch|OWNER branches|OWNER branch" docs_build/dev/ProjectInstructions -++``` -++ -++Result: PASS, no active OWNER-only branch workflow wording. -++ -++```powershell -++node -e "canonical owner, backlog, and Team Charlie ownership checks" - +``` - + - +Result: PASS - + - +## Targeted Results - + --+- PASS: ZIP-on-every-result rule exists. --+- PASS: hard stops require ZIP/report output. --+- PASS: `next logical PRs` plural wording exists. --+- PASS: automatic next PR planning is tied to completed PR ZIP review. --+- PASS: SOD/main active branch workflow remains present. --+- PASS: EOD clean main sync rule remains present. --+- PASS: Product Owner testable rule remains present. --+- PASS: page-level Playwright completion gate remains present. -++- PASS: canonical governance owner map exists. -++- PASS: Product Owner testable owner is canonicalized. -++- PASS: page-level Playwright owner is canonicalized. -++- PASS: API/environment owner is canonicalized. -++- PASS: branch lifecycle owner is canonicalized. -++- PASS: backlog includes owning team and next logical PR wording. -++- PASS: Team Charlie owns Sprites and Objects. - +- PASS: no runtime files changed. --+- PASS: no UI files changed. --+- PASS: no API files changed. --+- PASS: no database files changed. - + - +## Playwright - + +@@ -1,22 +1,12 @@ +-docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md +-docs_build/dev/ProjectInstructions/README.txt +-docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md +-docs_build/dev/ProjectInstructions/addendums/branch_context_governance.md +-docs_build/dev/ProjectInstructions/addendums/branch_lock_governance.md +-docs_build/dev/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md +-docs_build/dev/ProjectInstructions/addendums/codex_project_instructions_startup.md +-docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md +-docs_build/dev/ProjectInstructions/addendums/multi_team.md +-docs_build/dev/ProjectInstructions/addendums/pr_workflow.md +-docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md +-docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md +-docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md +-docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md +-docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md +-docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization.md +-docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_branch-validation.md +-docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_manual-validation-notes.md +-docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_requirements-checklist.md +-docs_build/dev/reports/PR_26177_OWNER_012-project-instructions-cleanup-backlog-canonicalization_validation-lane.md +-docs_build/dev/reports/codex_changed_files.txt +-docs_build/dev/reports/codex_review.diff ++M docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md ++M docs_build/dev/ProjectInstructions/standards/README.md ++A docs_build/dev/ProjectInstructions/standards/RUNTIME_RELIABILITY_ARCHITECTURE.md ++M docs_build/dev/ProjectInstructions/team_assignments/ACTIVE_TEAM_REGISTRY.md ++M docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md ++A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture.md ++A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_branch-validation.md ++A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_manual-validation-notes.md ++A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_requirement-checklist.md ++A docs_build/dev/reports/PR_26179_001-runtime-reliability-architecture_validation-report.md ++M docs_build/dev/reports/codex_changed_files.txt ++M docs_build/dev/reports/codex_review.diff