9de55e352d6d8342da94dda8ee51757d24ab2c8a
743
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
9de55e352d |
fix(cellular): one action per account a tick, never a refused tick
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 1m39s
Foundation / server-image (push) Successful in 5m19s
Foundation / image (push) Successful in 6m54s
Region 16 playtest: a bud showed and was then undone, and several buds were
refused. The client scheduled a discrete action at server tick + lead, but
movement runs ahead of that once the lead shrinks (each movement takes the
tick after the last one sent), so a bud could name a tick a movement already
had. A tick takes one action per account: the region refused the whole tick
and dropped every player's actions on it ("tick stalled ... error=4").
- Server: keep_one_action_per_account keeps each account's discrete action
(engulf, bud, become, emerge), else its newest, and refuses only the rest.
- Client: a discrete action is scheduled after every tick already sent, and
movement is held off the tick a queued discrete action owns.
- Failed background commits now log their category, publication error,
store error and SQLSTATE (never server text), to diagnose ok=0 commits.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
||
|
|
2ce8c3afb1 |
deploy(dev): promote 6de2b7b's images on region 16 (end a stranded life)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m40s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Gitea run 574: server 1d0585ef, postgres-tools c200bd43 (schema 69). The previous build 441c25a5 stays retained. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
6de2b7b1ca |
feat(admin): end a stranded life from the portal (schema 69)
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 6s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5m17s
Foundation / image (push) Successful in 6m23s
Foundation / server-image (push) Successful in 8m26s
ADR-0182 section 18. Region 16 refused every birth for an account with "Existing cell is already bound to this account" although no cell in it held the account: a published reservation was never ended, and the only remedy was tools/ops/end-account-life.sql as the database owner. - Account action POST /api/accounts/<uuid>/end-life?request=N. The admin API reads the life's region from the account's lives and refuses while that region's live view lists a cell holding the account (also a bud, split offspring or organism control moved to), a region it cannot view, an incomplete view, an unpublished request or a life no longer open. - Schema 69: admin_end_account_life_v1 (admin role only) ends it at the region's latest commit and appends who and why to admin_life_endings. - The account page shows End life for each published life not ended. - A region refusing a birth because the account holds a cell (life_exists) could never record it: reject_primitive_life accepted reasons 1..3 only. The reservation stayed open and unpublished and refused every later birth. Schema 69 and the C++ wrapper accept existing_life (4). - A region with no ticking cells ignored queued admin commands (such as a spawn) until something else woke it; a queued command now keeps it ticking until applied. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
8085392122 |
deploy(dev): promote 3c75397's images on region 16 (4,096-life ticks)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m33s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Gitea run 571: server 441c25a5 and postgres-tools 03a24875 (schema 68). The previous server build a7ab3f34 stays retained. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
3c753970c8 |
feat(cellular): region ticks of up to 4,096 lives for testing (schema 68)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 31s
Foundation / server-image (push) Successful in 4m29s
Foundation / image (push) Successful in 5m43s
ADR-0182 section 17. The plan's 2,000-organism cap became the rules-12 key region.organism_cap, which was parsed but never enforced; the real bound was max_cellular_tick_lives = 256 (ADR-0106), which rules 13's organism cap could not exceed. The bound is now 4,096, for testing limits only; the DEV tuning file keeps 256. - max_cellular_tick_lives (4,096) bounds the raw region path: step, owner state, batch trace (cellular_batch_bytes_for) and current checkpoint traces. max_cellular_frozen_lives (256) keeps cohort populations, population batches, migration traces and pre-v3 cellular traces, whose database checks are fixed. - Tuning: reproduction.organism_cap and wildlife_cap accept up to 4,096. - Schema 68: the trace checker under the current publishers (cellular_births_v45) accepts 4,096 intents, births and mutations per tick; spawn_wildlife takes up to 256 cells a command. - Region view and portal: the lineage archive's fill (births of 65,536, genomes of 4,096), at which a region stops ticking. - PostgreSQL suite: 256 wildlife spawned in one command, then a 289-life tick published and recovered exactly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
8005e7c4ae |
deploy(dev): promote 7573044's images on region 16 (take, cull, wildlife cap)
Foundation / checks (checks) (push) Successful in 6s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m43s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Gitea run 569: server a7ab3f34 and postgres-tools f2ce1192 (schema 67). The previous server build 87d607f5 stays retained. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
757304437e |
feat(admin): take reserve, cull wildlife, wildlife cap, fresh bud costs (schema 67)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m34s
Foundation / postgres-tools (push) Successful in 26s
Foundation / server-image (push) Successful in 4m30s
Foundation / image (push) Successful in 5m46s
ADR-0182 section 16, from playtesting region 16 at its 256-life cap. - Bud costs: the region host's cache of each genome's bud cost was keyed by genome only, so after a tuning adoption the client kept the old cost (or "cannot bud"). It now clears when the rules' encoding changes. - Wildlife cap: reproduction.wildlife_cap (optional, 0..organism cap, 0 = the organism cap) refuses buds of parents without an account at that many lives, keeping the slots above it for players. Bits 17-31 of the energy-cycle word, so older rules keep their bytes. DEV file: 200. - Schema 67: admin command kinds take_reserve (8: up to the amounts from a life's reserve to the spent pool) and remove_wildlife (9: every life without an account, as remove_cell). - Region view: caps; the portal shows lives against the cap. - Portal: Take reserve in the inspector, Remove all wildlife, and marking cells on the map (shift+click, shift+drag) for bulk removal; the guided editor lists optional keys the base revision lacks. - Client: a refused bud says the region may be full. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
51aa08446d |
deploy(dev): promote 9b854e6's server image on region 16 (open regions from the portal)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m39s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Gitea run 567: server sha256:87d607f5bc1cb6b8673767ad44d62d773fac4116b1f952cdb80fac61625b1d02 on the region, its hooks and the admin portal; 2f2d5c2b stays retained. The postgres-tools image stays at run 556's (no schema change). This sync also applies the portal's new egress and mounts Secret aevolution-admin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
9b854e6960 |
feat(admin): open a fresh region from the portal (ADR-0182 section 15)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m31s
Foundation / postgres-tools (push) Successful in 27s
Foundation / server-image (push) Successful in 4m33s
Foundation / image (push) Successful in 5m39s
The Regions page opens the next region in place of the one DEV serves: the admin API reads the region overlay, its kustomization, the grant broker and the portal deployment from main at one commit, rewrites only the region id, routes, genesis commit and seeded wildlife range (refusing files whose layout differs), commits them in one Gitea multi-file commit as aevolution-bot, then starts a full Argo sync of exactly that commit. The page follows the sync until the region is live, across the portal's own restart. Credentials come from Secret aevolution-admin mounted read-only as files (--deploy-config); without it the feature stays off. A small OpenSSL HTTPS client talks to Gitea (verified) and argocd-server (verification per ARGOCD_TLS_VERIFY). The portal's NetworkPolicy gains egress to the node's ingress for Gitea and to the argocd-server pods, as approved. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
e0f9512567 |
deploy(dev): promote 23ea240's server image on region 16 (guided tuning editor)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m44s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 6s
Gitea run 565: server sha256:2f2d5c2bd6baa68163d81cbdd75496e200e8446cf806f443834cd03bdb6eb828 on the region, its hooks and the admin portal; a8edb67c stays retained. The postgres-tools image stays at run 556's (no schema change). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
23ea24080e |
feat(admin): guided tuning editor that sends only the changes
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 28s
Foundation / server-image (push) Successful in 4m48s
Foundation / image (push) Successful in 5m37s
DEV's ingress refuses request bodies over about 1 KB, so adopting a whole revamp file (5 KB) failed with a 413 the portal misreported as the API's 64 KiB limit. POST /api/tuning?base=baseline|REV now takes only changed `key = value` lines, applies them to the baseline file or the newest revision (409 stale_base for an older one), keeping its comments, then checks and stores as before. The Tuning page becomes a guided editor: sections, a field per setting with its unit, plain reading and comment, a changes list with Check and Apply (or Adopt as is), and loading a past revision or the baseline as changes. The full-text editor stays as Text mode and names a proxy refusal plainly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
8dedde454d |
deploy(dev): promote cc2eaf2's server image on region 16 (energy cycle)
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m43s
Foundation / server-image (push) Successful in 5s
Gitea run 563: server sha256:a8edb67c9b69edb5c2c750a068c6d89553691fccc47a4241c67c12f3f9e2a0b2 on the region, its hooks and the admin portal; 12e62108 stays retained. The postgres-tools image stays at run 556's (no schema change). Region 16 keeps its recorded rules until the energy cycle is adopted as a tuning revision. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
cc2eaf2e05 |
feat(cellular): energy cycles back through the spent pool (ADR-0182 section 14)
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m42s
Foundation / checks (checks) (push) Successful in 6s
Foundation / checks (client) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 31s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / server-image (push) Successful in 4m45s
Foundation / checks (network) (push) Successful in 4s
Foundation / image (push) Successful in 5m31s
Energy cells used went to the region's heat store and never returned, so a region without photosynthesizers drained: region 16's wildlife ate its energy and starved, and its matter-only drip filled the deposit limit. Two optional rules-13 tuning keys, adoptable live: spent.heat_recycle_per_mille moves that share of the heat store to the spent pool at the end of every tick, before the drip (1,000 closes the loop and returns heat built up before), and spent.drip_absorb lets a drip at the deposit limit join the first existing bubble at or after its spot. Both use the reserved word after the offer interval, so rules without them keep their bytes, digests, checkpoints and replays. The DEV revamp file turns both on. The region view reports heat and the cycle; the portal counts heat in the region's energy and ledger. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
944f6719cf |
deploy(dev): promote c481a7f's server image on region 16 (map canvas fix)
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / image (push) Successful in 6s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m41s
Foundation / checks (client) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / server-image (push) Successful in 5s
Gitea run 561: server sha256:12e62108f7b920bea0b91f50b21fcabd2463af6f1e94242140bbde786e42eee5 on the region, its hooks and the admin portal; 9f76430c stays retained. The postgres-tools image stays at run 556's (no schema change). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
c481a7fe5e |
fix(admin): keep the region map canvas out of the layout
Foundation / checks (postgres) (push) Successful in 2m22s
Foundation / checks (ecs) (push) Successful in 2m23s
Foundation / checks (client) (push) Successful in 2m26s
Foundation / postgres-tools (push) Successful in 1m38s
Foundation / checks (network) (push) Successful in 2m22s
Foundation / server-image (push) Successful in 5m14s
Foundation / image (push) Successful in 6m17s
Foundation / checks (checks) (push) Successful in 2m27s
Foundation / checks (deploy) (push) Successful in 2m27s
Foundation / checks (tsan) (push) Successful in 5s
The map canvas is absolutely placed in its stage, so its backing size can never feed back into the page layout, and the backing store is capped at 2x and 4,096 pixels a side; a refused 2D context skips the paint instead of throwing. The tab bar no longer shows a vertical scrollbar, the overlays drop backdrop blur, and the theme icons are HTML entities. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
2fc50df26c |
deploy(dev): promote 6338cc9's server image on region 16 (admin region page)
Foundation / checks (checks) (push) Successful in 6s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m40s
Foundation / postgres-tools (push) Successful in 6s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Gitea run 559: server sha256:9f76430c33a33d246384dc198b4df3d7e4abf28277a2f435cce25696d01a4863 on the region, its hooks and the admin portal; ec473b40 stays retained. The postgres-tools image is unchanged (no schema change). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
6338cc9142 |
feat(admin): region page redesign, resource ledger, drip and dark mode
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m40s
Foundation / postgres-tools (push) Successful in 30s
Foundation / server-image (push) Successful in 4m46s
Foundation / image (push) Successful in 5m34s
The region view adds the rules-13 drip and complete counts and totals over every life and deposit. The region page is rebuilt around the map: a KPI strip (tick pace, population, deposit capacity, region energy and matter, spent pool, next drip), layer toggles that double as the legend, zoom and a scale, and tabs for inspecting cells and deposits, resources (where each channel sits, the spent pool and each channel's next drip), actions, the running tuning and session access. The admin API serves the region tuning file read only (--region-tuning). Light and dark themes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
68f2567253 |
deploy(dev): promote 7273b15's images on region 16 (live tuning)
Foundation / checks (checks) (push) Successful in 6s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m44s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
Server ec473b40 and postgres-tools 946de1a1 from Gitea run 556 (schema 66). de1b4b32 stays retained. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
7273b157d6 |
feat(admin): live tuning revisions adopted at recorded ticks (schema 66)
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m47s
Foundation / postgres-tools (push) Successful in 29s
Foundation / server-image (push) Successful in 4m42s
Foundation / image (push) Successful in 5m55s
ADR-0182 section 13. The admin portal's Tuning page edits the world's rules-13 tuning (the Git revamp file format); the admin API checks it, stores an append-only revision and queues an adopt_tuning admin command (kind 7: revision and rules digest) for every region of the world. - Lifecycle: adopt_tuning replaces the region's rules after births when a resolver names the rules for that revision and digest; the safety revision cannot change live. At most one adoption per batch. - Host: fetches the revision text, rebuilds and digests the rules before appending the command; publication and recovery name the rules from the successor state, checked against the recorded digest. - Schema 66: tuning_revisions, admin_set_tuning_v1, load_tuning_revision_v1 (runtime), admin_tuning_revisions_v1, admin_tuning_text_v1. - OpsServer: optional bounded request bodies (Content-Length, 413). - Region view: rules_sha256, so the portal shows each region's revision. - Portal: Tuning page; baseline from the mounted cellular-revamp.tuning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
7041c947a9 |
deploy(dev): promote 018b4b1's images on region 16 (resource schedules)
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m43s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Server de1b4b32 and postgres-tools ae4449c2 from Gitea run 554 (schema 65). db678279 stays retained. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
018b4b1817 |
feat(admin): resource schedules for bubbles, pool releases and wildlife (schema 65)
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 23s
Foundation / server-image (push) Successful in 4m38s
Foundation / image (push) Successful in 5m35s
ADR-0182 section 12: the game source as recurring admin commands. A schedule repeats add_bubbles, release_pool or spawn_wildlife every 1 s to 24 h while enabled; the region's pending-command read queues each due run as an ordinary command (recorded in the trace, bound once), never two waiting per schedule, so an idle region builds no backlog. Append-only schedule versions; admin API GET/POST /api/regions/<n>/schedules and a portal card to add, stop and start. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
2485a028bb |
deploy(dev): promote 070c458's images on region 16 (bans, logout, time played)
Foundation / checks (checks) (push) Successful in 6s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m42s
Foundation / image (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 6s
Foundation / server-image (push) Successful in 5s
Server db678279 and postgres-tools 5c10dfe9 from Gitea run 552 (schema 64). 03ce069d stays retained. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
070c458dc5 |
feat(admin): bans, admin logout and time played (schema 64)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 2m9s
Foundation / server-image (push) Successful in 5m23s
Foundation / image (push) Successful in 6m10s
ADR-0182 section 11. - Append-only account bans; a ban also revokes the account's grants (its live session closes at the next control renewal) and issue_account_grant refuses a banned account (EVL20 -> broker 403 account_banned). Lifting is another row. - admin_logout_account_v1 revokes by account id. - Session intervals recorded by claim/renew/release (signatures unchanged): time played, sessions and last seen per account. - The region view carries each cell's lineage root; the portal counts living wildlife descended from an account's lives. - Portal: Ban/Unban and Log out with reason and history; time played column. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
b3eca78549 |
deploy(dev): promote b1cc3b1's images on region 16 (admin commands, schema 63)
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m42s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Server 03ce069d and postgres-tools e9f04a09 from Gitea run 550: queued admin commands in trace 5 (spawn wildlife, bubbles, spent pool, remove, grant). 82e24842 stays retained. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
b1cc3b121b |
feat(admin): live admin commands in trace 5 (schema 63)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 30s
Foundation / server-image (push) Successful in 4m44s
Foundation / image (push) Successful in 5m33s
The admin portal can now spawn wildlife, add bubbles, add to or release the spent pool, remove a cell and grant a cell's reserve on a running rules-13 region (ADR-0182 section 10). No new owner format or region opening. - Trace 5: trace 4 plus 64-byte command records counted in the tick header's last word; a batch without commands stays trace 4 (older builds replay it). Bundle 15 admits trace 5. - CellularLives::admin_candidate applies a tick's commands after its births, each on a copy kept only when it applies and closes: imports through the boundary ledger, removals into the spent pool with a new `removed` corpse cause, spawned roots via the ADR-0180 seed (now a shared helper) funded by an exact import. Refused commands change nothing. - Schema 63: the immutable admin_commands queue (spawn identities from the life allocator), pending/history reads, and binding of every recorded command exactly once inside both cellular publishers; the SQL trace parsers read trace 5 through its trace-4 normal form. - The region polls pending commands every 2 s and appends up to 16 per tick; the admin API and portal gain region actions, per-cell Remove/Grant and the command history. - Fixes an existing test that did not advance its head after a tick commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
b075198040 |
deploy(dev): promote 46c1064's images on region 16 (session windows in SQL)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m36s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 6s
Foundation / image (push) Successful in 5s
Server 82e24842 and postgres-tools 4ab36349 from Gitea run 548: schema 62 session windows and the admin group role. d4b62521 stays retained. Sync only after the aevolution_admin role exists and aevolution-admin-pg uses its login; sessions stay closed until a window is opened in the admin portal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
46c106409e |
feat(admin): session windows in SQL, opened from the admin portal (schema 62)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m33s
Foundation / postgres-tools (push) Successful in 2m14s
Foundation / server-image (push) Successful in 5m21s
Foundation / image (push) Successful in 6m18s
The dev session window moves from Git to SQL (ADR-0087 amendment): the admin portal opens, extends (30 min to 4 h from now) and closes it, and the cellular region re-reads it every 5 s with --session-window-source db. No push, sync or restart per window; a closed window keeps the region running instead of crash-looping. - Schema 62: append-only session_windows (4 h cap, no rewrites), load_session_window_v1 for the runtime group, admin_set_session_window_v1 and admin_session_windows_v1 for a dedicated admin group role, granted and audited each migration run when EVO_PG_ADMIN_ROLE is set (aevolution_admin in DEV). Schema 61's views are revoked from the runtime group. - RegionSessions admission switch: while closed every Hello is refused before signature work and closing closes open sessions (new sessions were still admitted after expiry before). - Admin API: GET/POST /api/regions/<n>/session-window, window state in the regions list; the portal's session-window card with history. - Git: REGION_SESSION_WINDOW and the pre-push refresh rule are removed; the policy check requires the database source and refuses a committed window. Needs the new image and the aevolution_admin role (with the portal's login in aevolution-admin-pg) before a sync. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
510ecaee80 |
deploy(dev): promote 4adcc7b's server image on region 16; retain 1dd1ea05
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m41s
Foundation / postgres-tools (push) Successful in 6s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 6s
Server image d4b62521 from Gitea run 546 (
|
||
|
|
4adcc7b638 |
fix(admin): accept OAuth callback query strings
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m42s
Foundation / postgres-tools (push) Successful in 1m43s
Foundation / server-image (push) Successful in 5m17s
Foundation / image (push) Successful in 6m2s
|
||
|
|
d851717b7b |
deploy(dev): promote bc1eeb9's images on region 16 (admin portal, schema 61)
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m37s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Server and postgres-tools images from Gitea run 544 (
|
||
|
|
bc1eeb970b |
deploy(dev): refresh the session window for the admin portal push
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m34s
Foundation / postgres-tools (push) Successful in 2m1s
Foundation / server-image (push) Successful in 4m59s
Foundation / image (push) Successful in 6m17s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
54beceb823 |
feat(admin): read-only admin portal and API (ADR-0182 step 1, schema 61)
evo-admin-api serves the portal at srs.aeternalisgames.com and read-only JSON for world 100 behind Keycloak (realm role aevolution-admin, audience aevolution-admin, client aevolution-admin-portal): accounts with session, status, lives, deaths, resets and mutation choices; one account's lives; the world's regions; and a live 2D region view of cells, wildlife, pools and bubbles. The portal is plain HTML/CSS/JS with PKCE sign-in, a strict CSP and no third-party code. - Schema 61: three bounded SECURITY DEFINER read functions, fenced in the privilege audit; no table or existing function changes. - Cellular regions answer GET /admin/view on the ops port (NetworkPolicy: Prometheus and the admin portal only); CellularLives::extent_of reads the existing phenotype budget. No simulation, checkpoint or wire change. - TokenVerifier takes an optional realm role and returns the email; the ops server's response bound is configurable (16 KiB default unchanged). - DEV component admin-portal-dev (Deployment, Service, NetworkPolicies); the Ingress and the aevolution-admin-pg Secret are created out of band. - CI scripts pinned to schema 60 now expect 61. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
46e5ea6c5d |
test(postgres): provision the Git revamp rules without the DEV wildlife fixture
Since
|
||
|
|
f047cd8833 |
deploy(dev): restore evo-sim Harbor digest
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m40s
Foundation / postgres-tools (push) Successful in 5s
Foundation / image (push) Successful in 5s
Foundation / server-image (push) Successful in 6s
|
||
|
|
477ea8980b |
deploy(dev): promote d46de25's images on region 16; ADR-0182 admin portal
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m38s
Foundation / postgres-tools (push) Successful in 6s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Server and postgres-tools images from Gitea run 540 (
|
||
|
|
d46de25bef |
Refresh session window for authenticated publication
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m38s
Foundation / server-image (push) Successful in 6m15s
Foundation / postgres-tools (push) Successful in 6m21s
Foundation / image (push) Successful in 7m42s
|
||
|
|
d0e0e2cf87 | Record reproduction trial publication authentication limit | ||
|
|
5416590f9e | Add reproduction safety trial and resizable cellular panels | ||
|
|
7ca5f74f03 | fix(client): keep nutrient readouts on stable single-line rows | ||
|
|
82d21e65b2 |
deploy(dev): open region 16 on 51f979a's image - even split, 130% collection
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m32s
Foundation / server-image (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 21s
Foundation / image (push) Successful in 4m41s
Region 16 keeps region 15's tuning (100 seeded wildlife, triple food, half the bud fee) and adds feeding.split_evenly = 1 and feeding.collection_percent = 130: food sources share the matter limit equally between the nutrients they hold. Its 100 wildlife take IDs 900000003716-900000003815. The grant broker routes accounts to region 16; region 15 stays stored and 736bf98's build stays retained. Refreshes the session window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
51f979a664 |
feat(cellular): split collection evenly across a source's nutrients
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m31s
Foundation / postgres-tools (push) Successful in 21s
Foundation / server-image (push) Successful in 4m21s
Foundation / image (push) Successful in 5m3s
Playtest: phosphorus held growth back everywhere. Per-nutrient collection limits followed the body recipe (5% phosphorus), but the membrane is 10% phosphorus, so no cell could collect phosphorus as fast as it builds with it. Two optional revamp tuning keys, stored in a formerly reserved rules word so regions opened without them keep their exact meaning: - feeding.split_evenly: matter from one food source is split equally between the nutrients it holds (a carbon-only bubble gives the whole matter limit to carbon, carbon and phosphorus half each, all four a quarter each), each share scaled by the cell's collection trait; - feeding.collection_percent: every collection limit per cent (100 default). The DEV tuning file takes these keys with the image that reads them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
054e48579c |
deploy(dev): open region 15 - 100 seeded wildlife, triple food, half bud fee
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m29s
Foundation / server-image (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 19s
Foundation / image (push) Successful in 4m50s
Maintainer tuning for the next playtest, on the current server image: - 100 starting wildlife (was 32) on their own ADR-0180 identity range, 900000003616-900000003715; - every pool and bubble holds three times region 14's food; - the nursery funds 256 founders' worth (was 64), so the wildlife leave room for player births; - the bud fee scale drops to 50%. The grant broker routes accounts to region 15; region 14 stays stored. Refreshes the session window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
d057374148 |
fix(client): stabilize HUD and anchor draggable panels
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m29s
Foundation / postgres-tools (push) Successful in 20s
Foundation / server-image (push) Canceled after 1m43s
Foundation / image (push) Canceled after 1m43s
|
||
|
|
840816c541 |
deploy(dev): promote 736bf98's server image on region 14 (life endings)
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m27s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
A player's death is now recorded under the reservation's lineage root, so an account that became an offspring, a bud or an organism can be born again. Region 14 keeps running; 8a48e40's build stays retained. Refreshes the session window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
736bf98aaa |
fix(server): end a player's life under the reservation's root identity
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m27s
Foundation / postgres-tools (push) Successful in 26s
Foundation / server-image (push) Successful in 4m18s
Foundation / image (push) Successful in 5m4s
Playtest: after becoming a split's offspring and being engulfed, every new
birth was refused ("Existing cell is already bound to this account"). The
region recorded the ending under the dead cell's own identity, which was never
reserved, so the database ignored it and the founder's reservation stayed
open. After Adhesion the opposite happened: the merged founder's ending closed
the reservation while the player lived on as the organism.
An account's life now ends only when no life holds the account, and the ending
names the lineage root (cellular_lineage_root): the life born from the
reservation, reached through parent links in lives and corpses.
tools/ops/end-account-life.sql lets the operator end one stranded account's
reservation (dry run unless confirm=yes; exactly one match required).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
||
|
|
5dab8e4018 |
deploy(dev): promote 8a48e40's server image on region 14 (bud fee fix)
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m29s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
Region 14 stalled at tick 6068 on the short bud fee; this image refuses such a bud instead. Committed history is unchanged, so region 14 resumes. Run 529's build stays retained. Refreshes the session window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
8a48e405fd |
fix(lifecycle): a bud's fee comes on top of its cost, or the bud is refused
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m28s
Foundation / postgres-tools (push) Successful in 22s
Foundation / server-image (push) Successful in 4m21s
Foundation / image (push) Successful in 5m1s
DEV region 14 stalled at tick 6068 with a conservation error. The bud fee was checked against the reserve before funding the bud, then deducted with a clamp after: a parent whose reserve covered the bud but not the fee as well paid less than the fee while the region reclaimed all of it, creating matter. The fee was zero until the budding playtest tuning, so it never showed. Funding now requires the reserve left after the bud to cover the fee; a parent that cannot is refused for insufficient funding, and the fee is subtracted exactly. No committed tick changes: a short-fee bud never committed. The regression runs seeded wildlife under the DEV fee until a bud (it failed with the conservation error before this fix). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
467402e404 |
deploy(dev): open region 14 on run 529's image (seeded wildlife, bud fee)
Foundation / checks (checks) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m33s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Run 529 (
|
||
|
|
ff121c3ed1 |
feat(cellular): seed dev wildlife and tune budding playtests
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m27s
Foundation / postgres-tools (push) Successful in 30s
Foundation / server-image (push) Successful in 4m16s
Foundation / image (push) Successful in 4m54s
|
||
|
|
18a64a29cd |
deploy(dev): promote run 15b4342's server image on region 13
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m39s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Shows what holds growth back and each nutrient's flows (session v14 body block). Region 13 keeps running; run 525's build stays retained. Refreshes the session window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |