maniator / maniator/verticopolis
[Feature]: [P3] D25 condo-stickiness test horizon margin (watch-only)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Imported from the engineering backlog (
_bmad-output/implementation-artifacts/backlog.md, storycondo-stickiness).
Priority P3 (do-first order) | Severity: low (test-only) | Status: open | Epic: — | Type: review-deferral | Recorded: 2026-07-05
Problem / motivation
Gated (watch-only). D25's horizon margin is thinner (deterministic, not flaky; watch-only, no code change now). With the gentle condo noise rate, a permanent noisy neighbor reaches a notice at ≈151 game-hours; faqComplete.test.ts D25/D25b loop 24*8=192, a fixed ~41-tick (~27%) cushion. Safe today (fully deterministic), but coupled to CONDO_NOISE_EROSION and the 24*8 horizon, if either is retuned, re-derive time-to-notice and widen the loop. (Edge Case Hunter, CONDO_NOISE_EROSION.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in faqComplete.test.ts and inspect the D25/D25b loop using the 24*8 horizon, along with the CONDO_NOISE_EROSION reference in the issue. Re-derive the time-to-notice if either value changes; done means confirming the deterministic cushion remains safe or widening the loop when it does not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100