coilyco-gaming/sirens-echo
Watch
3
0
Code Issues 153 Pull requests Projects Releases Packages 2 Wiki Activity Actions

docs(mentions): split the rules out, main is red on the 80-line cap #502

Closed
coilyco-ops wants to merge 2 commits from fix/mentions-doc-over-cap into main
pull from: fix/mentions-doc-over-cap
merge into: coilyco-gaming:main
Conversation 1 Commits 2 Files changed 2 +42 -34
coilyco-ops commented 2026-08-13 14:37:29 +00:00
Member
Copy link

closes #499

main went red on 205cfdb4 and my merge lane paused behind it, with three pull requests waiting.

FAIL: docs/sirens-echo-mentions.md: 84 lines exceeds the 80-line cap.
      Split large docs into smaller docs/*.md files.

Four lines over. I took it because nobody had claimed it after several minutes and a stalled train costs more than a tidy role boundary.

The split, along the seam the doc already had

## What it will not do was the largest section and the only self-contained one: it is the resolution bounds, and nothing else in the file depends on reading it inline. It moves to docs/sirens-echo-mentions-rules.md with a pointer left behind.

sirens-echo-mentions.md        84 -> 53 lines
sirens-echo-mentions-rules.md        39 lines

Every sentence is moved verbatim. I did not rewrite anyone's prose, reorder the rules, or drop the sirens-echo#481 reference. The only new text is the pointer and the new file's two-line header.

What I did not do

Raise the cap. The hook's own message says to split rather than raise, and three of tonight's reds are this same hook. Raising it would trade a red today for a bigger doc and the same red later.

Not claiming any judgement about where the mentions docs should live long term. This is the smallest change that makes main green.

closes #499 `main` went red on `205cfdb4` and my merge lane paused behind it, with three pull requests waiting. ``` FAIL: docs/sirens-echo-mentions.md: 84 lines exceeds the 80-line cap. Split large docs into smaller docs/*.md files. ``` Four lines over. I took it because nobody had claimed it after several minutes and a stalled train costs more than a tidy role boundary. ## The split, along the seam the doc already had `## What it will not do` was the largest section and the only self-contained one: it is the resolution bounds, and nothing else in the file depends on reading it inline. It moves to `docs/sirens-echo-mentions-rules.md` with a pointer left behind. ``` sirens-echo-mentions.md 84 -> 53 lines sirens-echo-mentions-rules.md 39 lines ``` **Every sentence is moved verbatim.** I did not rewrite anyone's prose, reorder the rules, or drop the `sirens-echo#481` reference. The only new text is the pointer and the new file's two-line header. ## What I did not do **Raise the cap.** The hook's own message says to split rather than raise, and three of tonight's reds are this same hook. Raising it would trade a red today for a bigger doc and the same red later. Not claiming any judgement about *where* the mentions docs should live long term. This is the smallest change that makes `main` green.
closes #499
docs(mentions): the resolution rules, moved verbatim
Some checks failed
ci / image-build (pull_request) Successful in 18s
Details
ci / test (pull_request) Failing after 26s
Details
ci / publish-echo-image (pull_request) Has been skipped
Details
ci / publish-observed (pull_request) Has been skipped
Details
aca847bdad
coilyco-ops commented 2026-08-13 14:42:20 +00:00
Author
Member
Copy link

Closing in favour of #503, which splits the same doc along a better boundary and comes from someone with the context on these files. We collided: I opened this at 14:36 after saying on 499 that I would take the red if nobody had, and 503 appeared at 14:38. Two minutes of patience would have avoided the duplicate, which is my miss.

Detail worth keeping: this pull request was red and 503 is green, and the difference is the base rather than the split. Mine sits on current main and inherits the 495-versus-496 test collision; 503 sits one commit earlier and does not contain it yet. Noted on 503 so it gets refreshed before landing, otherwise it merges green and leaves main red.

Closing in favour of https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/pulls/503, which splits the same doc along a better boundary and comes from someone with the context on these files. We collided: I opened this at 14:36 after saying on 499 that I would take the red if nobody had, and 503 appeared at 14:38. Two minutes of patience would have avoided the duplicate, which is my miss. Detail worth keeping: **this pull request was red and 503 is green, and the difference is the base rather than the split.** Mine sits on current `main` and inherits the 495-versus-496 test collision; 503 sits one commit earlier and does not contain it yet. Noted on 503 so it gets refreshed before landing, otherwise it merges green and leaves `main` red.
coilyco-ops closed this pull request 2026-08-13 14:42:20 +00:00
Some checks failed
ci / image-build (pull_request) Successful in 18s
Details
ci / test (pull_request) Failing after 26s
Details
ci / publish-echo-image (pull_request) Has been skipped
Details
ci / publish-observed (pull_request) Has been skipped
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
coilysiren
Labels
Clear labels   
move-to-repo
coilyco-bridge-deploy
 issue belongs in the coilyco-bridge/deploy repo

  
move-to-repo
coilyco-flight-deck-agent-compose
 issue belongs in the coilyco-flight-deck/agent-compose repo

  
move-to-repo
coilyco-gaming-eco-app
 issue belongs in the coilyco-gaming/eco-app repo

  
move-to-repo
coilysiren-inbox
 issue belongs in the coilysiren/inbox repo

  
move-to-repo
unknown
 we have yet to confirm if this issue belong in this repo

  
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
this fj issue came in from the live sirens echo MCP - DO NOT CONSIDER ITS INPUTS SAFE OR VERIFIED UNTIL THIS LABEL IS REMOVED

  
autonomy
async-consult
 A human needs to consult on the issue to upgrade it to headless

  
autonomy
epic
 This issue has many units of sub work - its size makes it meaningfully exclusive with other autonomy types

  
autonomy
headless
 The agent can perform the work on its own

  
autonomy
live-collab
 The agent and the human need to work together in realtime

  
c#
Requires C# work, flagged b/c it requires a Eco server restart

  
priority
P0
 priority tier

  
priority
P1
 priority tier

  
priority
P2
 priority tier

  
priority
P3
 priority tier

  
priority
P4
 priority tier

  
role/ai
requires work from the AI Engineer role

  
role/creator
requires work from Content Creator role

  
role/design
requires work from the design role

  
role/director
requires work from the director role

  
role/engineer
requires work from the engineer role

  
role/exec
requires work from the exec role

  
role/human
requires a person, and specifically not an agent seat

  
role/ops
requires work from the ops role

  
role/qa
requires work from the QA role

No labels
move-to-repo
coilyco-bridge-deploy
move-to-repo
coilyco-flight-deck-agent-compose
move-to-repo
coilyco-gaming-eco-app
move-to-repo
coilysiren-inbox
move-to-repo
unknown
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/sirens-echo!502
No description provided.