docs: preserve Gemini Fable+Astra remediation planning artifacts

[sayed710]

Summary

Preserves Gemini's five 2026-09-30 planning artifacts at historical target 553751c628f69436600987ddbf649a13f2b9eb2d and adds independent Codex adjudication against current main 07946b9b03538ed73a3f7b773e7ad5a327d83805. Historical statements remain attributed to Gemini; explicit corrections and a disposition ledger distinguish implemented work, genuine open work, superseded guidance, owner decisions and deferred proposals.

Main was merged normally into the existing branch, without conflicts or history rewriting. Effective scope is seven Markdown files under docs/audits/: the five preserved artifacts, audit navigation, and CODEX_GEMINI_PLANNING_ADJUDICATION_2026-10-02.md. No production code, tests, CI, deployment or configuration changes.

Corrections and current-main adjudication

• Repairs all five local repository links in the planning index.
• Verifies historical/current scrypt, gambit-theme, locally stored gambit-session handle/userId, absence of game-state sessionStorage, and current locale/auth metadata; marks the original inaccurate inventory as historical.
• Corrects the unsupported claim that Docker already embeds Git SHA/repository URL. VITE_GIT_SHA / VITE_REPO_URL remain proposed plumbing.
• Corrects Game Review to the server API, 40 reviewed-player moves and existing partial-review metadata; proposed extensions remain unselected server-contract choices.
• Explicitly schedules remaining production Arabic catalog/release acceptance and separates casual challenges from rating dependencies.
• Harmonizes D-02 labels in detail and response sheet without selecting an option; records the original discrepancy and explicitly identifies menu/Settings surfaces as proposed work requiring implementation and guest access.
• Reclassifies merged feat: durable, exactly-once ratings with explicit variant × speed pools (P0) #76 ratings, feat(web): production-grade typed localization and chess bidi foundation #81 localization infrastructure/runtime/bidi and feat(api): add moderation operations and production trust workers #83 report/triage/first-admin/trust-worker/Helm reporter/launcher work as implemented. Production Arabic, approved policy/source surfaces and later report/triage web UI remain open.
• Adjudicates all 14 P1 entries and 17 candidate owner decisions, including existing unavailable/profile/responsive capabilities, stale paths, unsupported certainty claims and intentionally deferred P2/P3 scope.

No owner checkbox is selected. Preservation and adjudication do not approve product decisions, legal text, permanent visual direction or feature implementation. This does not replace the authoritative original audit, visual handoff, recovery provenance or append-only project history.

Validation and reviews

All eight repository check:* guards pass. Documentation checks verify all 75 relative links/anchors, balanced fences, historical SHA preservation, unchanged unselected checkbox counts, no remaining file:///docs/ repository links and a documentation-only effective diff. Whitespace checks pass against current main. The topology guard initially lacked local Playwright dependencies; clean npm ci restored those dependencies and the guard passed. No runtime test execution is claimed for this docs-only PR.

Exact final HEAD: b5b00b634aea567b704afd09bf6e77ec163e3286. Fresh GitHub/portal evidence:

• Qodo Bugs 0 / Rule violations 0. The valid absent-menu finding is Resolved. Portal PR80 Pending/all-types Findings 0; complete All states inventory is one finding, Resolved. Remaining requirement gaps/actionables 0, no omitted warning. Qodo labels its latest docs-only pass Skipped while updating resolution evidence to the exact final head; this is not represented as a new Deep pass. Summary.
• Greptile reviewed exact final HEAD, 5/5, all prior findings addressed, zero new actionable issues. Seven files reviewed, zero comments added; check 110815732126 SUCCESS. Summary.
• Review threads: 0 unresolved out of 8.
• Configured CI/pin-parity exclude these audit Markdown paths: zero Actions runs on exact head, no runtime CI claimed. Applicable PR checks Greptile and supplementary CodeRabbit SUCCESS; CodeRabbit skipped automatic review under its repository policy.
• Fresh independent hierarchy: Gemini 3.8 Flash High genuine HTTP429 quota, then Claude Sonnet 4.6 Thinking genuine HTTP429 quota. Allowed Codex strict self-review CLEAN on exact final HEAD, zero actionable findings. Older a1 Claude CLEAN is historical, not the final independent evidence.
• Fresh fetch: local = remote branch = GitHub PR HEAD; remote divergence 0 0, main 3 ahead / 0 behind; worktree clean. No force/main push or history rewrite.

PR #80 remains OPEN and unmerged. No force push, main push or replacement PR.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 1a718e47-b918-4936-aa74-e0b2ba47a0ec

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📜 Skill insights (0)

1. Language choices rely on absent menus ✓ Resolved

Description

The revised D-02 Option B says to place the language control in an existing avatar menu and mobile
drawer, while Option A also assumes a mobile menu. The current shell has neither, so selecting
either option would leave the implementation plan missing the menu work needed to make the control
accessible.

Code

docs/audits/GEMINI_OWNER_DECISION_DOSSIER_2026-09-30.md[161]

+  * **Option B:** User/Settings Menu Only (All Viewports). Place a "Language / اللغة" row inside the existing user avatar menu dropdown (and mobile drawer).

Relevance

●●● Strong

Accepted precedents favor correcting documentation that describes absent capabilities as existing.

PR-#35
PR-#78

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The changed option describes an existing avatar menu and mobile drawer, but the shell markup
contains navigation links and standalone auth, logout, and theme controls, with no such menu or
drawer.

docs/audits/GEMINI_OWNER_DECISION_DOSSIER_2026-09-30.md[156-164]
packages/web/index.html[16-45]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The harmonized language-switcher options assume an existing avatar menu and mobile drawer, but the current shell has neither.

## Fix Focus Areas
- docs/audits/GEMINI_OWNER_DECISION_DOSSIER_2026-09-30.md[156-165]

## Recommended Fix
Describe the menu and drawer as proposed UI that must be built if the owner selects an option requiring them. Correct the D-02 current-state inventory without selecting an owner option.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

Review mode: ⏭️ Skipped: The latest push only makes substantive wording corrections in two Markdown audit artifacts, with no runtime, configuration, schema, test, or CI behavior affected.

Tip of the day

💡 Did you know, you can show, collapse, or hide each part of a finding: code, evidence, and all

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Previous reviews

Review updated until commit b5b00b6

Results up to commit a1a9d10 🧠 Deep

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Language choices rely on absent menus ✓ Resolved

Description

The revised D-02 Option B says to place the language control in an existing avatar menu and mobile
drawer, while Option A also assumes a mobile menu. The current shell has neither, so selecting
either option would leave the implementation plan missing the menu work needed to make the control
accessible.

Code

docs/audits/GEMINI_OWNER_DECISION_DOSSIER_2026-09-30.md[161]

+  * **Option B:** User/Settings Menu Only (All Viewports). Place a "Language / اللغة" row inside the existing user avatar menu dropdown (and mobile drawer).

Relevance

●●● Strong

Accepted precedents favor correcting documentation that describes absent capabilities as existing.

PR-#35
PR-#78

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The changed option describes an existing avatar menu and mobile drawer, but the shell markup
contains navigation links and standalone auth, logout, and theme controls, with no such menu or
drawer.

docs/audits/GEMINI_OWNER_DECISION_DOSSIER_2026-09-30.md[156-164]
packages/web/index.html[16-45]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The harmonized language-switcher options assume an existing avatar menu and mobile drawer, but the current shell has neither.

## Fix Focus Areas
- docs/audits/GEMINI_OWNER_DECISION_DOSSIER_2026-09-30.md[156-165]

## Recommended Fix
Describe the menu and drawer as proposed UI that must be built if the owner selects an option requiring them. Correct the D-02 current-state inventory without selecting an owner option.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

PR Summary by Qodo

Preserve Gemini remediation planning and decision artifacts

📝 Documentation 🕐 40+ Minutes

AI Description

• Preserve five Gemini planning artifacts covering localization, policy disclosure, P1 sequencing,
 and candidate owner decisions.
• Record evidence provenance and targeted corrections so superseded proposals remain distinguishable
 from current recommendations.
• Mark all proposals as pending Codex review and owner approval; production behavior remains
 unchanged.

Diagram

graph TD
  B["Existing audits"] --> X["Planning index"] --> I["EN/AR plan"] --> D["Decision dossier"] --> G{"Review gate"}
  X --> P["Policy plan"] --> D
  X --> S["P1 sequencing"] --> D

Loading

High-Level Assessment

Keep the indexed, topic-specific evidence snapshots with their correction history and explicit approval boundaries. Consolidating them into one document would make the separate plans and their provenance harder to review; no different implementation architecture is warranted for this documentation-only handoff.

Files changed (5) +1222 / -0

Documentation (5) +1222 / -0

GEMINI_I18N_PLANNING_2026-09-30.mdDocument staged EN/AR localization and bidi planning +145/-0

Document staged EN/AR localization and bidi planning

• Inventories hardcoded UI strings, mixed-direction notation requirements, and proposed tests. Preserves the correction that narrows the first proposed PR to headless infrastructure, deferring production Arabic copy and switcher placement.

docs/audits/GEMINI_I18N_PLANNING_2026-09-30.md

GEMINI_OWNER_DECISION_DOSSIER_2026-09-30.mdCollect unselected candidate owner decisions +679/-0

Collect unselected candidate owner decisions

• Presents 17 candidate decisions with options, dependencies, deadlines, and an unselected response sheet. Separates legal-counsel questions from proposed product choices and engineering invariants.

docs/audits/GEMINI_OWNER_DECISION_DOSSIER_2026-09-30.md

GEMINI_P1_SEQUENCING_2026-09-30.mdInventory P1 gaps and proposed execution waves +166/-0

Inventory P1 gaps and proposed execution waves

• Records the assessed status of 14 P1 capabilities, including dependencies on active PR #76 and candidate owner decisions. Proposes four implementation waves while identifying work that can proceed independently.

docs/audits/GEMINI_P1_SEQUENCING_2026-09-30.md

GEMINI_PLANNING_INDEX_2026-09-30.mdIndex planning artifacts and correction provenance +98/-0

Index planning artifacts and correction provenance

• Registers the four specialized dossiers against their evidence snapshot and traces targeted corrections to earlier proposals. States that the artifacts do not supersede authoritative audits or authorize implementation.

docs/audits/GEMINI_PLANNING_INDEX_2026-09-30.md

GEMINI_POLICY_DISCLOSURE_PLANNING_2026-09-30.mdDocument policy and AGPL disclosure planning boundaries +134/-0

Document policy and AGPL disclosure planning boundaries

• Inventories proposed policy surfaces and source-disclosure needs. Preserves the correction that limits initial work to scaffolding and defers policy text, consent UX, navigation placement, and legal sufficiency determinations.

docs/audits/GEMINI_POLICY_DISCLOSURE_PLANNING_2026-09-30.md

[greptile-apps]

Confidence Score: 5/5

[Low risk] Adds historical planning documents to the audit archive.

The documentation changes appear safe to merge.

Summary

The PR preserves five historical Gemini planning artifacts and adds a current-main adjudication ledger. Since the previous review, it clarifies that D-02 menu and Settings surfaces are proposed implementation, not existing shell features.

• All seven earlier findings are addressed in the current documentation.
• No new actionable issue was identified in the final-head changes.

_{Reviews (3) · Last reviewed commit: "docs: identify language-switcher menu su..."}

[sayed710]

/review

[sayed710]

@greptileai review

Please review exact final HEAD a1a9d10e0d482f56178203c3cdada626102b0751 against current main 07946b9b03538ed73a3f7b773e7ad5a327d83805. This docs-only refresh preserves the historical Gemini snapshot and adds a complete Codex correction/disposition ledger. All seven original findings were independently verified and corrected explicitly; historical false statements are labeled and superseded rather than silently erased. Please assess any remaining actionable factual, provenance, owner-authority or documentation-integrity findings on this exact head.

[qodo-code-review]

Code review by qodo was updated up to the latest commit a1a9d10

[sayed710]

/review

Please review exact final HEAD b5b00b6 against main 07946b9. The valid D-02 absent-menu finding is corrected: actual shell inventory is explicit; menu/drawer/Settings surfaces are proposed UI needing implementation and guest access if selected. Historical claim is attributed/superseded, all owner options remain unselected. Scope remains seven docs/audits Markdown files. Please provide fresh Bugs, Rule violations and requirement gaps/actionable findings evidence; older-head reviews are stale.

[sayed710]

@greptile-apps Please review exact final HEAD b5b00b6 against integrated main 07946b9. The additional Qodo correction identifies D-02 menu/Settings UI as proposed implementation rather than existing shell features. Please check the complete documentation diff, provenance and zero remaining actionable findings. The seven original findings were verified fixed/superseded and their threads resolved after your a1a9d10 review; that earlier review is stale for the new HEAD.

[qodo-code-review]

Code review by qodo was updated up to the latest commit b5b00b6