Dune/docs/CURRENT_STATUS.md

Current development status

Updated 27 September 2026. The full twelve-faction goal is unfinished. Basic is playable and the six classic factions have a user-authorized Advanced preview. Expansion starts and full rules/publication acceptance remain gated.

Current checkpoint and work

The live NAS Apps dune image is the immutable ghcr.io/quintine/dune:sha-c9a3625ff2a9ddafdbc08e64de809eca6029db85 from successful container workflow 36358270534. The public footer's title and accessibility name show that full revision; visible text shows c9a3625. After the update, owner sign-in succeeded and nine existing rooms remained, including a playing room at version 54. A fresh 0600 online SQLite backup in the persistent app volume passed PRAGMA quick_check before the update. The earlier temporary remote plaintext owner key and provisioning SQL were removed. Private saved-seat reconnection, complete historical-data comparison and live Diplomat retreat gameplay were not exercised; its local behavior is verified, not production gameplay-proven.

The bounded Discovery Orgiz Collection transfer is connected in current local source for Basic/Advanced, with an automatic public log and saved continuation. It treats each positive collected board deposit as one observable blow, a source inference pending a publisher clarification. A focused engine/browser/SQLite checkpoint is in Discovery prototype; this code is not yet in the live c9a3625 image. Contested/shared transfers and full Discovery release acceptance remain gated.

Checkpoint 209fb18 was pushed and its matching container workflow 36359970371 completed successfully. The dedicated deployment agent could not enter TrueNAS Apps because the host desktop was OS-locked; it made no NAS change, backup or post-rollout claim. Production remains at the last verified c9a3625 image until the Apps session is unlocked and this exact image is deployed.

The bounded Fremen Nexus Cunning prototype connects an initially empty worm's public offer, one spent private card, a Karama response, a typed remote ride after the Nexus, human controls and minimal legal AI in classic-faction Nexus-only games. Basic/Advanced natural continuation, an additional-worm placement and an actual Advanced special-Karama summon retain their physical parent, response and native-then- remote ride order across JSON/isolated SQLite recovery and duplicate CAS. Natural and summoned offer/ride browser surfaces were exercised. Review found and fixed an inherited-key force-custody bypass. A second Cunning offer inside an interrupted control, Great Maker, combined modules, Secret Ally protection and complete Nexus games remain gated.

The bounded Ecaz Nexus Betrayal path lets a card holder select one public territory shared by Ecaz and its ally before the first Shipment and Movement turn advances. One spent card, a provisional Karama response and exact typed ally-force return are wired through human controls, legal bot action, JSON and in-memory SQL continuation, and focused gameplay, race and restart tests. A local browser fixture rendered the holder-only offer and rival Karama notice without writing a room. Secret Ally inquiry, Duke Cunning and combined modes remain gated. The main page labels its build's Git commit in the lobby and active-table masthead; local Git HEAD does not represent uncommitted work. The main-branch container workflow publishes an image but does not deploy the live site automatically.

Current work adds discussion moderation: owners/operators can mute or unmute new public/private messages from a human seat. History, incoming messages, game state and credentials remain saved; the setting follows recovery/handover. Atomic authority/version fences, durable audit and exact admin/message retries are connected. This is partial participant support; access revocation, participant removal, assisted recovery, permanent deletion, bulk actions and backup/operations tools remain unfinished.

Participant AI checkpoint 2cddf03 is pushed. Types/lint, 5,408 offline tests, 52 HTTP tests, build, twenty-two administrator HTTP groups and desktop/mobile browser acceptance passed. Deployment delivery was unconfirmed at that checkpoint; the current production revision is recorded above. No strategic AI refinement was added.

Readable-notice checkpoint 137f922 is pushed. Types/lint, 5,381 offline tests, 52 HTTP tests, build and delayed-response desktop/mobile browser QA passed. Its new-revision deployment handoff is pending confirmation.

The readable-notice follow-up extends first-request progress to admin operations, AI permissions and seat handovers, preventing recovery instructions from flashing before a successful response. Seat recovery/handover confirmations remain above the table until Continue. Existing retry proofs and rules/AI pacing are unchanged. New-revision deployed acceptance remains separate from local checks; positive production admin testing still needs authorized access.

The connected administrative archive/unarchive prototype lets closed rooms leave the default directory without changing saved games, credentials, discussion or AI deadlines. Unarchiving leaves play closed; reopening requires unarchiving first. Exact saved retries and combined archive / removal filters preserve recovery. Permanent deletion, bulk actions and full participant/backup support remain unfinished.

Checkpoint 98b1b32 added close/reopen and passed types/lint, 5,356 offline tests, 52 HTTP tests and build, with seventeen administrator HTTP groups and lost-response desktop/mobile browser QA. It is deployed on the NAS: container verification passed, migration 0013 applied, all eight prior rooms and ten seats were preserved, and public HTTPS/browser saved-seat restoration passed. Anonymous admin routes remain denied. Positive production administrator acceptance still awaits authorized QA access. Archive checkpoint e918e2e is also deployed: migration 0014, integrity and public HTTPS/browser saved-seat restoration passed; all eight prior rooms and ten seats were preserved. Its positive production administrator acceptance remains pending the same authorization.

Checkpoint 238de38 added recoverable removal/restoration and passed types/lint, 5,314 offline tests, 52 HTTP tests and build, with fourteen administrator HTTP groups and lost-response desktop/mobile browser QA. It is deployed on the NAS: container verification passed, migration 0012 applied, all eight prior rooms and ten seats were preserved, and public HTTPS/browser saved-seat restoration passed. Anonymous removal and other admin routes remain denied. Positive production administrator acceptance remains pending authorized QA operator access.

Checkpoint c0cc4de added neutral administrator lobby configuration and passed types/lint, 5,260 offline tests, 52 HTTP tests and build, with eleven dedicated administrator HTTP groups and lost-response desktop/mobile browser QA. It is deployed on the NAS: container verification passed, migration 0011 applied, all eight prior rooms and ten seats were preserved, and public HTTPS/browser saved-seat restoration passed. Anonymous creation, control and configuration requests remain denied. Positive production administrator acceptance remains pending authorized QA operator access.

Checkpoint e7d4efc added administrator room creation and passed types/lint, 5,240 offline tests, 52 HTTP tests and build, with independent review and eight dedicated administrator HTTP groups. It is deployed on the NAS: container verification passed, migration 0010 applied, all eight prior rooms and ten seats were preserved, and a saved seat restored through public HTTPS and the browser. Anonymous administrator creation remains denied. Positive production administrator acceptance still requires explicitly authorized QA operator access.

Checkpoint 8c922b4 added pause/resume and joining locks and passed types/lint, 5,223 offline tests, 52 HTTP tests and build, with independent review and dedicated local administrator/browser checks. It is deployed on the NAS: container verification passed, migration 0009 applied, all eight prior rooms and ten seats were preserved, and a saved seat restored through public HTTPS. Anonymous administrator requests remain denied. Authenticated production admin acceptance still requires the pending QA-access confirmation.

Checkpoint f29d056 was pushed and deployed to the NAS instance. Readable create/join progress and Continue notices passed actual HTTPS browser acceptance, including mobile and saved-seat refresh; existing production records survived the update. Administrator sign-in renders closed by default. Authenticated admin production checks remain pending provisioning approval.

The readable-notice fix replaces the flashing recovery screen during ordinary room creation/join with concise progress. Actual recovery instructions stay until resolved, and completed-action text waits for a local Continue control. It does not add confirmation steps to game rules or AI turns.

Administrator access/directory checkpoint c2d392e passed types, lint, 5,196 offline tests, 52 HTTP tests and build, plus focused authenticated/browser checks. Its authenticated production acceptance remains pending; the current deployment preserves saved games and full administration gates.

The user added a complete administration panel to the goal on 22 September: secure admin access, room creation/removal and lifecycle controls, participant support, backup/restore, operational views and audited actions. The first prototype now connects separate administrator sign-in, persistent sessions/revocation and a searchable, filtered, paginated room directory at /admin. Private game contents remain excluded. Operator provisioning and recovery instructions are in the admin guide. Room creation, lifecycle/removal, participant support, backups and operational controls remain unfinished; these belong before full AI refinement/calibration. Existing rules, Git, subagent and preservation requirements remain in force.

The goal also requires testing the deployed application at https://dune.procrastination.games. Match the running revision, exercise relevant real player/admin flows in dedicated QA rooms, and record deployed results separately from local checks. See production verification. This requirements update does not claim a new deployed test result.

Earlier completed rules checkpoint: 0f79f28, forced Harkonnen exchange return. Types, lint, 5,150 offline tests, 49 HTTP tests and the production build passed. One complete Advanced sample had no rejected actions across 158 actions and four JSON restores. Browser inspection and exact refresh were checked; full visual acceptance remains open. All 1,586 prior rooms and 3,354 human seats were preserved; new QA/HTTP rooms brought the baseline to 1,626 rooms and 3,442 seats.

Current work exposes Advanced preview through normal room creation and host lobby controls. It uses genuine setup, explicit unfinished-mode start, renewed human readiness after mode changes, private seat restoration and saved continuation. Six classic factions, existing Tech Tokens (3+ players) and Stronghold Cards are admitted; expansion/module gates and pending rulings remain. Focused engine, controls, retry and concurrent recovery checks are connected; final independent review, browser, sample-game and required checks accompany the Git checkpoint. Preview access does not certify complete rules compliance.

The Sandmaster/HMS source comparison found no official clarification that passengers remaining in the interior trigger collection from outside territories during native relocation. A ruling question was sent; ordinary HMS relocation and force entry/exit remain working. No extra collection is silently applied. The Bureaucrat/Emperor gift question and the other recorded skill boundaries remain pending.

The reviewed remaining native Ecaz/Moritani effects, Duke revival and Richese empty-cache auction arithmetic still cross recorded source questions. Native Tleilaxu revival now creates its skill offer at successful commitment, including automatic response chains; the former dependency is resolved in its Basic profile. The 8f7a62c policy checkpoint removed usage checks/cutoffs and deferred full AI work until feature completion, followed by three adjacent 75% targets.

The platform audit found no supported Sites scheduler or Durable Object provisioning contract. Durable unattended bot resumption remains blocked on that capability; request/reconnect continuation does not establish it. Preserve pending rules questions and mode gates.

The connected Harass & Withdraw prototype supports either battle-card slot, private category inspections, exact undialed normal/elite returns, opponent-Traitor cancellation, mandatory disposal, controls and all four AI profiles. New battles also have revealed physical allocation for ordinary/elite mixtures and multi-sector returns. Richese card combinations and additional optional modules stay gated. Withdrawal before explosion and card-specific discard precedence are explicitly labeled inferences. The Stone Burner timing question is pending; no user answer is assumed. Reinforcements remains unfinished. This does not open variant, mode or publication gates.

The preceding early Sapho aggressor connects the printed battle-priority effect during the existing shared pre-plan opportunity. Physical attacker/defender/chooser stay stable; Habbanya takes precedence in either slot. Shared priority feeds Stone admission, ordinary/Stone resolution, public controls and all four AI profiles. Battle-bound history survives private saved continuation. Later intervention remains unfinished; no new ruling is assumed. Final checks, samples, browser evidence and delivery belong to the source-bound private report and Git message.

The Mirror admission review found that every genuine Richese setup contains the unresolved copied weapons. Ordinary-only activation cannot safely depend on hidden custody or alter the printed deck. Mirror remains gated pending the existing disposal ruling and copied-choice work. Continue with independent missing faction/card functions, then integrated play and refinement.

The Smuggler follow-up review supports a saved reveal-time receipt with settlement only on leader survival, but located no official ruling on modified leader strength. The user has been asked about Kwisatz/trainer/Stunner composition; no answer is assumed. See the source follow-up.

Authoritative navigation

• Rules checklist, topic implementation-checklist and each feature's entries: track implementation, controls, AI, documentation and verification, plus Missing, Prototyped, Integrated, Verified and Polished stages.
• Rule decision index: settled contracts, source precedence and pending material interpretations. Consult it before reopening research.
• Development guide and verification tools: architecture, focused checks, source-bound reports, reusable faction samples, private backup and saved-seat restoration.
• Implementation history: newest first. Historical evidence and outage records stay there and in feature documents; read bounded relevant sections and verify old absence claims against current code/tests.
• Efficiency pilot: the first three milestones are pushed; measurement limits remain explicit. Reuse tools and checks, without promising an unmeasured savings percentage.

Connected development capabilities

These links define bounded working behavior, not complete module certification.

Area	Current connected work and evidence
Base/Advanced setup	Normal Advanced preview, genuine setup, Advanced study, Fremen cancellation, Atreides full-plan audit. Earlier Basic-then-flip fixtures do not establish current setup coverage.
Expansion factions	Ixians/Tleilaxu and all seven faction selections: genuine setup, Ecaz six-force placement and Advanced Loyalty, separate optional card variants, private controls and saved per-lot Ixian/Richese decline. Actual special-lot exchange remains pending.
Leader Skills	Common lifecycle, known skilled capture, Mentat question preview, Bureaucrat payments, five battle disciplines, Planetologist, Suk Graduate, Rihani and other battle effects, Smuggler shipment, No-Field and battle collection, Sandmaster routes and worm rides, Banker spending, Diplomat defense and bounded retreat. Remaining bands and combinations are explicit in those contracts.
Discoveries	Prototype: genuine setup, Great Maker, seven cards/eight tokens, inspection and stash rewards, nested sites, signed later free entry, carried Ornithopter, sole Cistern, bounded Orgiz transfers, Jacurutu income, Testing Station and Shrine. Orgiz's per-deposit interpretation, contested/shared benefits and mixed physical allocation remain provisional or pending. The Orgiz path in current source is not yet deployed.
Nexus/Homeworlds	Decision index links each integrated faction family, native/borrowed effects, physical custody, private choices, payments and transport. CHOAM Secret Ally trade and bounded after-victory inspection and Emperor extra revival are connected; the CHOAM universal winner window is a privacy-preserving product inference, not publisher text, and Emperor purchase remains pending. A source audit or helper alone is not a completed effect.
Truthtrance	Spice facts, card counts, hand inventory, recorded knowledge, and Basic/no-Guild Advanced reserve-shipment promises use authoritative private state. Earlier readiness audits do not supersede these follow-ups.
Other cards	Sapho runtime includes first among remaining unstarted movement turns after Advanced Guild has finished. Recruits connects clean Revival play; Harass & Withdraw connects the bounded battle return in the same independent three-card preview. Richese card contracts and the checklist identify other connected effects and explicit gaps.
Multiplayer	Public and private discussion, saved rooms/seats, recovery, uncertain-request retry, own-seat AI, named-player AI permission and voluntary seat handover have connected controls and recovery evidence.

Remaining readiness

Area	Remaining gate
Basic core	Ordinary Guild repricing/transport settlement, broader truthful commitments, unresolved special timing and integrated rules/human/AI acceptance.
Six-faction Advanced	Base gaps, provisional special-Karama outcomes, remaining timing audits and authentic multiplayer/browser acceptance. The user-authorized unfinished preview is available; setup matrices and complete samples do not certify full compliance.
Twelve factions and all optional modules	Every missing effect, remaining skill bands, Ecaz card variant, Kull Wahad, unfinished Richese cards, Terror effects, occupation entitlement, Nexus interactions, contested Discoveries and complete games across valid combinations. Detailed boundaries remain in the checklist/decision index.
AI	Maintain minimal legal participation and critical correctness fixes while game features are unfinished. Full implementation, strategy refinement and calibration wait until all non-AI features are complete; then target approximately 75% higher-tier wins for Medium/Easy, Hard/Medium and Brutal/Hard. See the AI development plan. These targets remain unverified.
Multiplayer	Broader disconnected/abandoned-seat recovery, unattended continuation and network-failure acceptance, while preserving authoritative versioning, custody, privacy and saves.
Administration	Complete the admin panel: permissions, room directory and creation/removal, lifecycle controls, participant support, backup/restore and operational audit tools. Required before full AI refinement.
Components and experience	Full component inventory/text verification, all readable inspectors, original artwork, animation/sound/accessibility/mobile polish, complete internal guidance and end-to-end human play.

AI calibration, multiplayer audit, component inventory and visual playtest record their measured scope. README retains publication gates.

Working sequence and preservation

Prototype every remaining function in dependency order, using existing controls, legal AI and the saved-state model. Continue independent functions while material rulings are pending. Then run integrated games, repair failures, deepen combination and recovery coverage, and complete all non-AI features. Only then fully implement and refine AI strategy and calibrate the adjacent difficulty pairs. Keep focused checks for crashes, deadlocks, legality, custody and privacy; complete required broad checkpoint checks. Use selective subagents and independent review for complex rules/privacy/persistence. Commit and push verified checkpoints under “Push all from now on”, verify push success. The user removed the usage cutoff and routine account-usage checks; efficient work, Git delivery and selective subagents remain required.

The user-authorized 13 September reset happened once; preserve all games created since it. Keep .wrangler/state, credentials and private backup artifacts out of Git. Reuse a healthy server; restart only for a relevant change or observed problem, with a fresh backup, safe human-play boundary and verified restoration. No hourly restart or recurring maintenance automation is installed; do not recreate one.