Repository navigation
Open
Labels
Description
π€ Generated by the Agentic Engineer
Needs you
1. Ask #5006
Title
keep World at Ruin's witness on AWS, or self-host it in the cluster?
Question
Follow-up to #4978 and your reply on the [2026-11-13 digest](https://github.com/devantler-tech/monorepo/issues/5005#issuecomment-6846682844): "A, but could World at Ruin's witness be self-hosted in the cluster instead?"
Yes, it can be self-hosted. World at Ruin keeps a small "witness" record for each game zone. Its only job is to notice when the game's saved data has been put back to an older copy, so an old copy can never hand out a zone twice. The witness can only do that if putting the game's data back cannot also put the witness back. Amazon's database gives us that for free, because a restore there always makes a new table that anyone can tell is new. That is why AWS was chosen in devantler-tech/world-at-ruin#1341.
Inside the cluster, the witness would be a small separate database on the platform, using a database the platform already runs. It would catch bugs and a restore of only the game's own database, which is the most likely kind of restore. But a restore of the whole platform, or of the witness's disk, would put both back together, and nothing could tell. That case would move outside what the design proves. Which do you want?
Options
- **A. Keep AWS, as planned in #4978.** I prepare a draft platform pull request for one narrow AWS role, and you review and merge it yourself. The trial table is tiny and short-lived. The design keeps its full guarantee.
- **B. Self-host in the cluster.** No AWS is needed. I rewrite devantler-tech/world-at-ruin#1443 as an in-cluster trial: the witness gets its own small database, kept out of the platform's backups. I record in the game's design that a whole-platform or disk restore is outside the proof. Later, the public witness network (C2SP) could restore outside checking without an AWS account, once it accepts production logs.
- **C. Not now.** #1443 stays parked, and the four World at Ruin cards stay blocked as started work.
Recommendation
**A.** It is the only option that keeps the guarantee the design was chosen for. It uses an AWS account you already run. B is a sound choice if you are fine with a whole-platform restore falling outside the proof.
If unanswered
I make no AWS change and do not rewrite the trial. #1443 stays parked with this ask as its blocker. I read your reply on #4978 as conditional on this question, so I do not treat it as a go-ahead for A.
2. Ask #5034
Title
How much log and trace history should Coroot keep?
Question
How much log and trace history should Coroot keep?
Options
- **A. One full previous day.** Grow each ClickHouse volume to about 35 Gi, and set Coroot's retention to 2 days to match.
- **B. A full week.** Grow each ClickHouse volume to about 130 Gi, which keeps the configured 7 days.
- **C. Today only.** Keep 15 Gi, set retention to match what fits, and close the "logs from 3 days ago" requirement as not wanted.
Recommendation
**A.** It is the smallest change that keeps yesterday's history while an incident is investigated overnight. It needs about 40 Gi more storage across the two replicas, against about 230 Gi more for B. I will ship the volume and retention change as a reviewed platform PR.
If unanswered
Coroot stays at today-only history (option C in practice), and the "3 days ago" requirement on platform#6143 stays open. The separate read-only retention check continues either way.
3. Ask #5041
Title
decide the eleven World at Ruin look-and-feel previews
Question
For each preview on the page, should it be switched on for every player, improved first, or removed?
Options
Answer per preview with its issue number and one letter, for example `947: A, 950: C`:
- **A. Switch on.** It becomes what every player sees, and its launch setting is deleted.
- **B. Improve first.** Name the one gap to close. It stays off until that is done.
- **C. Remove.** The preview and its launch setting are deleted, and the current look stays.
The eleven: #336 layered outfit pickers, #405 walk, #459 control hints, #563 cave-foot talus, #577 drifting ash, #613 regional foliage, #868 run, #947 cloth material, #950 wrap drape, #1275 waist refinement, #1287 regional stone.
Recommendation
Start with the four overdue ones; the page puts them side by side. From the front, back and side pictures: **947: A** (the stitched weave reads as worn cloth, where the shipped one looks like a flat printed check), **950: C** and **1275: C** (from the front the drape barely changes the outline, and removing it also retires the waist setting that depends on it). I have no recommendation on the other eight; they need your eye on the pictures. Saved characters keep their shape and equipment whatever you choose, and each answer becomes one small reviewed pull request.
If unanswered
All eleven stay switched off, players keep today's looks, and the eleven issues stay open waiting on this question. Nothing is switched on because a date has passed or tests are green.
What shipped
Platform
New
- Company Email can now send to outside addresses. Production's mail server sends through Amazon's mail relay, with its own send-only login, and may reach nothing else on the internet. (#6252, #6236, #6173)
- The platform is ready to serve devantler.tech, its www name and the customer portal for the business site, and the hold on the business site's staging entry point is lifted. (#6188, #6214)
Improved
- The secrets service can now move to a new release safely: its three servers are replaced one at a time, each only after health and quorum checks pass and production has applied the change. This unblocks an update that had waited over a month. (#6213, #6241)
- Why production changes took six to twelve hours to deploy is now measured and decided: the merge queue is fast, but its jobs wait for shared build machines. (#6207)
KSail
Fixed
- Saying no to
ksail cluster deletenow leaves the cluster exactly as it was. Before, it had already disconnected the cluster's image mirrors, so a later delete left them behind. (#8359) - When a K3s cluster command fails, KSail now shows k3d's own reason, such as a port already in use, instead of always blaming Docker. (#8358)
Improved
- Every update of a Hetzner cluster now says whether a reserved floating address is left over and unused, not only updates that change the endpoint. (#7838)
Agent Improver
- Agents can no longer tie up a session with a foreground loop that keeps asking GitHub for news; they wait with a background watcher instead. (#5029)
- The digest check no longer mistakes numbers inside links for phone numbers, so a correct summary is not held back. (#5033)
What's in progress
- Eleven finished World at Ruin looks wait on your judgement; four are past their decision dates. (#5041)
- How much log and trace history monitoring should keep waits on your choice. (#5034)
- A probe that checks sign-in protection now goes through the public entry point; its first run from
mainwill say whether the protection holds on every route. (#6251)
How to reply
Reply on this GitHub issue (or to its notification email) with an ask's number and your choice, for example 1: B, or the number, a colon and your own words, for example 3: your words.
Your reply posts publicly, as a comment on this issue in the public devantler-tech/monorepo repository.
Reacted by coderabbitai
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
None yet
Projects
- StatusShow more project fieldsπ₯ Backlog
Activity
coderabbitai commentedon Nov 15, 2026
π Related PRs
#4476 - fix(automation): send daily unanswered maintainer asks [merged]
π Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.π§ͺ Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:π¬ Have feedback or questions? Drop into our discord!
chore: agent-claim #5072 nonce=06d935d1b566c0c6a256645392e0ce29
chore: agent-claim #5072 nonce=17172f991fa2e4c35fbfcbd2f6aabc73
devantler commentedon Nov 15, 2026
1:A
2:A
3:A