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

Reconcile retained model-opaque Community harness refactor #73

New issue
Closed
opened 2026-08-06 03:58:01 +00:00 by coilyco-ops · 5 comments
coilyco-ops commented 2026-08-06 03:58:01 +00:00
Member
Copy link

Preserved branch evidence

  • Branch: feat/sirens-community-harness
  • The branch retains one unique 16-file refactor promoting Echo to a model-opaque Community harness.
  • The branch has no pull request.
  • Current main contains the earlier Community harness work but not this retained promotion as an equivalent patch.

Account for the retained refactor against current main before deleting the branch.

## Preserved branch evidence * Branch: `feat/sirens-community-harness` * The branch retains one unique 16-file refactor promoting Echo to a model-opaque Community harness. * The branch has no pull request. * Current `main` contains the earlier Community harness work but not this retained promotion as an equivalent patch. Account for the retained refactor against current `main` before deleting the branch.
coilyco-ops commented 2026-08-07 19:11:27 +00:00
Author
Member
Copy link

Disposition: recommend closing as superseded

feat/sirens-community-harness now has a pull request, #77, and it does not merge. mergeable: false, 16 files, +192 / -84.

The reason is supersession, not a routine rebase. The merge base is 9a7a3fb dated 2026-07-28. main has advanced 28 commits in the ten days since, and several of them deliver this branch's purpose by a different route:

  • 5e9df6b and #68, 2026-08-04 and 2026-08-05, decoupled Echo from role-intent routes.
  • a033ea6, 2026-08-05, added deployment-selectable response profiles.
  • 5704293, 2026-08-05, named the DeepSeek profile Sirens Deep and added agent/sirens-deep.json.
  • f869390, 2026-08-05, preserved DeepSeek reasoning across tool turns.
  • bcc5998 and 6362e32, 2026-08-06, defined the CoilyCo general-purpose harness and moved harness definitions to YAML.

main is model-opaque today. This branch is the July 28 approach to a problem main solved differently and more completely.

This issue's original framing holds up: the branch content is genuinely absent from main. What changed is the conclusion drawn from that. Absent diff is not unmet purpose.

Before closing

Diff the branch against current main and confirm nothing in those 16 files is uniquely valuable. The strong prior is that everything is superseded, but that is a prior, not a verification, and this issue exists precisely to account for the branch rather than assume.

If the diff is clean, close #77 as superseded, delete the branch, and close this issue with that disposition recorded. If something unique survives, cherry-pick only that.

Do not attempt to resolve the conflicts and merge. Reconciling a ten-day-old parallel approach into a repository that already ships the capability adds risk with no gain, twelve days before coilysiren/inbox#324.

## Disposition: recommend closing as superseded `feat/sirens-community-harness` now has a pull request, #77, and it does not merge. `mergeable: false`, 16 files, +192 / -84. The reason is supersession, not a routine rebase. The merge base is `9a7a3fb` dated 2026-07-28. `main` has advanced 28 commits in the ten days since, and several of them deliver this branch's purpose by a different route: * `5e9df6b` and #68, 2026-08-04 and 2026-08-05, decoupled Echo from role-intent routes. * `a033ea6`, 2026-08-05, added deployment-selectable response profiles. * `5704293`, 2026-08-05, named the DeepSeek profile Sirens Deep and added `agent/sirens-deep.json`. * `f869390`, 2026-08-05, preserved DeepSeek reasoning across tool turns. * `bcc5998` and `6362e32`, 2026-08-06, defined the CoilyCo general-purpose harness and moved harness definitions to YAML. `main` is model-opaque today. This branch is the July 28 approach to a problem `main` solved differently and more completely. This issue's original framing holds up: the branch content is genuinely absent from `main`. What changed is the conclusion drawn from that. Absent diff is not unmet purpose. ## Before closing Diff the branch against current `main` and confirm nothing in those 16 files is uniquely valuable. The strong prior is that everything is superseded, but that is a prior, not a verification, and this issue exists precisely to account for the branch rather than assume. If the diff is clean, close #77 as superseded, delete the branch, and close this issue with that disposition recorded. If something unique survives, cherry-pick only that. Do not attempt to resolve the conflicts and merge. Reconciling a ten-day-old parallel approach into a repository that already ships the capability adds risk with no gain, twelve days before https://forgejo.coilysiren.me/coilysiren/inbox/issues/324.
coilyco-ops commented 2026-08-07 19:14:44 +00:00
Author
Member
Copy link

Diff read: do not merge, and the reason is stronger than supersession

Diffed origin/feat/sirens-community-harness against main at 6362e32. One commit on the branch, 714d718. 28 commits on main since the 9a7a3fb merge base.

The branch adds role-intent routing. main deliberately removed it.

The entire commit replaces the literal AGENT_PROXY_MODEL tag with a logical role/intent route resolved by Agent Proxy:

  • Config.AgentProxyModel becomes Config.AgentProxyRoute plus Config.Intent.
  • Definition gains Harness, Intents, and DefaultIntent.
  • A new Definition.LogicalRoute(intent) returns role + "/" + intent, producing keys such as community/knowledge-retrieval.
  • ProxyClient swaps Model/Role/Seat for Route/Intent/Harness, and sends the route in the model field.
  • AGENT_PROXY_MODEL is dropped from required configuration.
  • Schema bumps to sirens-discord-ops.agent.v3, with a hard check that harness == "sirens-discord-ops" and role == "community".

That is exactly what #67 and #68 took out on 2026-08-04 and 2026-08-05 under the title "Remove role-intent routing from Sirens Echo," and it matches the direction recorded in coilysiren/inbox#323, which holds that multi-harness role-intent routing is unproven.

It would also revert the profile architecture. Confirmed on main: no LogicalRoute, no AgentProxyRoute, no DefaultIntent, no route-intent concept anywhere in internal/, cmd/, or agent/. main selects the model through AGENT_PROXY_MODEL and selects behavior through YAML profiles at agent/sirens-echo.yaml and agent/sirens-deep.yaml, schema coilyco-harness.agent.v1. The branch expects JSON definitions at schema sirens-discord-ops.agent.v3 and hard-requires role == "community", which the CoilyCo general-purpose profile is not.

Those two designs cannot both be true in one tree. The conflicts are the architecture disagreeing with itself, not drift.

Recommended disposition

Close #77 without merging, delete feat/sirens-community-harness, and close this issue recording that the branch was superseded by the profile and YAML-harness work and contradicts the accepted removal of role-intent routing.

Nothing in the 16 files is worth cherry-picking on its own. The Go changes are all in service of the routing model being rejected, and the doc changes describe that model.

If logical routing is ever revisited, it should start from main's profile architecture rather than from this branch.

## Diff read: do not merge, and the reason is stronger than supersession Diffed `origin/feat/sirens-community-harness` against `main` at `6362e32`. One commit on the branch, `714d718`. 28 commits on `main` since the `9a7a3fb` merge base. **The branch adds role-intent routing. `main` deliberately removed it.** The entire commit replaces the literal `AGENT_PROXY_MODEL` tag with a logical `role/intent` route resolved by Agent Proxy: * `Config.AgentProxyModel` becomes `Config.AgentProxyRoute` plus `Config.Intent`. * `Definition` gains `Harness`, `Intents`, and `DefaultIntent`. * A new `Definition.LogicalRoute(intent)` returns `role + "/" + intent`, producing keys such as `community/knowledge-retrieval`. * `ProxyClient` swaps `Model`/`Role`/`Seat` for `Route`/`Intent`/`Harness`, and sends the route in the `model` field. * `AGENT_PROXY_MODEL` is dropped from required configuration. * Schema bumps to `sirens-discord-ops.agent.v3`, with a hard check that `harness == "sirens-discord-ops"` and `role == "community"`. That is exactly what #67 and #68 took out on 2026-08-04 and 2026-08-05 under the title "Remove role-intent routing from Sirens Echo," and it matches the direction recorded in https://forgejo.coilysiren.me/coilysiren/inbox/issues/323, which holds that multi-harness role-intent routing is unproven. **It would also revert the profile architecture.** Confirmed on `main`: no `LogicalRoute`, no `AgentProxyRoute`, no `DefaultIntent`, no route-intent concept anywhere in `internal/`, `cmd/`, or `agent/`. `main` selects the model through `AGENT_PROXY_MODEL` and selects behavior through YAML profiles at `agent/sirens-echo.yaml` and `agent/sirens-deep.yaml`, schema `coilyco-harness.agent.v1`. The branch expects JSON definitions at schema `sirens-discord-ops.agent.v3` and hard-requires `role == "community"`, which the CoilyCo general-purpose profile is not. Those two designs cannot both be true in one tree. The conflicts are the architecture disagreeing with itself, not drift. ## Recommended disposition Close #77 without merging, delete `feat/sirens-community-harness`, and close this issue recording that the branch was superseded by the profile and YAML-harness work and contradicts the accepted removal of role-intent routing. Nothing in the 16 files is worth cherry-picking on its own. The Go changes are all in service of the routing model being rejected, and the doc changes describe that model. If logical routing is ever revisited, it should start from `main`'s profile architecture rather than from this branch.
coilyco-ops commented 2026-08-11 04:30:05 +00:00
Author
Member
Copy link

Correction to advice given elsewhere in the 2026-08-10 session.

While auditing stray branches I reported that feat/sirens-community-harness, codex/sirens-echo-deepseek-profile-20260805, feat/thread-scoped-replies, and issue-67 were orphaned pre-squash lineage and safe to prune. The evidence was that git merge-base origin/main <branch> returns nothing for each, and that diffing one against main shows roughly 2974 deletions.

That evidence is accurate and the conclusion drawn from it was too strong. No shared history does not mean no unique content, which is exactly what this issue records for feat/sirens-community-harness: one retained 16-file refactor that main does not contain as an equivalent patch.

So the branch-level advice stands only for branches already reconciled. feat/sirens-community-harness should not be deleted until this issue is resolved, and the other three deserve the same read before anyone prunes them rather than a merge-base check alone.

Confirmed safe to delete, since they are merged and carry nothing unique: docs/drop-private-image-claim, fix/policy-check-image-context, sirens-deep-admission-hardening, and feat/prompt-snapshots.

Correction to advice given elsewhere in the 2026-08-10 session. While auditing stray branches I reported that `feat/sirens-community-harness`, `codex/sirens-echo-deepseek-profile-20260805`, `feat/thread-scoped-replies`, and `issue-67` were orphaned pre-squash lineage and safe to prune. The evidence was that `git merge-base origin/main <branch>` returns nothing for each, and that diffing one against `main` shows roughly 2974 deletions. That evidence is accurate and the conclusion drawn from it was too strong. **No shared history does not mean no unique content**, which is exactly what this issue records for `feat/sirens-community-harness`: one retained 16-file refactor that `main` does not contain as an equivalent patch. So the branch-level advice stands only for branches already reconciled. `feat/sirens-community-harness` should not be deleted until this issue is resolved, and the other three deserve the same read before anyone prunes them rather than a merge-base check alone. Confirmed safe to delete, since they are merged and carry nothing unique: `docs/drop-private-image-claim`, `fix/policy-check-image-context`, `sirens-deep-admission-hardening`, and `feat/prompt-snapshots`.
coilyco-ops commented 2026-08-12 11:54:31 +00:00
Author
Member
Copy link

Approved: close unmerged, delete the branch, close this issue

Direction from Kai, 2026-08-12 session.

The disposition recommended in the two comments above is accepted in full:

  1. Close PR #77 without merging.
  2. Delete feat/sirens-community-harness.
  3. Close this issue recording that the branch was superseded by the profile and YAML-harness work, and that it contradicts the accepted removal of role-intent routing in #67 and #68.

Nothing is cherry-picked. The Go changes are all in service of the routing model that was rejected, and the doc changes describe that model.

The retained refactor is now accounted for, which is what this issue existed to do. Absent diff was not unmet purpose.

If logical routing is ever revisited, it starts from main's profile architecture rather than from this branch.

Note on the third comment

The correction about branch pruning stands and outlives this issue. codex/sirens-echo-deepseek-profile-20260805, feat/thread-scoped-replies, and issue-67 still deserve a content read rather than a merge-base check before anyone prunes them. That is not tracked here — file it separately if it matters.

## Approved: close unmerged, delete the branch, close this issue Direction from Kai, 2026-08-12 session. The disposition recommended in the two comments above is accepted in full: 1. Close PR #77 without merging. 2. Delete `feat/sirens-community-harness`. 3. Close this issue recording that the branch was superseded by the profile and YAML-harness work, and that it contradicts the accepted removal of role-intent routing in #67 and #68. Nothing is cherry-picked. The Go changes are all in service of the routing model that was rejected, and the doc changes describe that model. The retained refactor is now accounted for, which is what this issue existed to do. Absent diff was not unmet purpose. If logical routing is ever revisited, it starts from `main`'s profile architecture rather than from this branch. ## Note on the third comment The correction about branch pruning stands and outlives this issue. `codex/sirens-echo-deepseek-profile-20260805`, `feat/thread-scoped-replies`, and `issue-67` still deserve a content read rather than a merge-base check before anyone prunes them. That is not tracked here — file it separately if it matters.
coilyco-ops commented 2026-08-12 12:27:12 +00:00
Author
Member
Copy link

Accounted for. Nothing to port.

The branch shares no history with main

$ git merge-base origin/main origin/feat/sirens-community-harness
fatal: no merge base

It is an orphan lineage, not a divergence. Its commits carry the earlier coily and coilyco-ai ancestry (lockdown: regenerate from coily release, Sync catalog-block check from coilyco-ai canonical), so it predates the history main grew from. That is why it cannot be diffed as a patch and why "reconcile" has to mean comparing behavior rather than comparing trees.

Tip is 714d718, 2026-07-28, and it is the 16-file refactor this issue names.

What the retained refactor actually does

Reading 714d718 rather than its subject line, the promotion is a routing change:

  • Config.AgentProxyModel becomes Config.AgentProxyRoute
  • the definition schema goes sirens-discord-ops.agent.v2 to v3 and gains harness, role, intents, and default_intent
  • SIRENS_ECHO_INTENT selects an intent, and definition.LogicalRoute(intent) derives the route from it
  • AGENT_PROXY_MODEL stops being required

So model opacity is achieved there by having the definition declare a set of intents and computing a logical route from the selected one.

Why it must not be merged

That is role-intent routing, which #67 and #68 deliberately removed and which #76 records as the reason PR #77 is not a prerequisite for anything. Merging it would reintroduce the mechanism the profile architecture was built to replace.

main already has the outcome, by a different mechanism

The goal of the refactor was that the harness names no model. main satisfies that:

  • no tracked definition carries a model field at all, verified across agent/*.yaml
  • the route is AGENT_PROXY_MODEL, read from the environment at runtime, so the deployment owns it and the repository never states it
  • the definition schema is coilyco-harness.agent.v1, which has no model, intent, or route field to state one with

main is model-opaque because a definition cannot name a model. The branch got there by letting the definition declare intents and derive a route. The stricter of the two is the one already shipped.

Verdict

The retained refactor is superseded, not lost. Its outcome is present on main and its mechanism is one the repository has since rejected on purpose. There is nothing to port.

On deleting the branch

I have not deleted it. Branch deletion is destructive and outside what I take on my own, and the tip is the only place that lineage exists. It is safe to delete on this analysis whenever you want it gone.

Worth noting separately: eighteen other branches are still on the remote, several clearly merged. If a sweep is wanted that is its own issue rather than a side effect of this one.

## Accounted for. Nothing to port. ### The branch shares no history with `main` ``` $ git merge-base origin/main origin/feat/sirens-community-harness fatal: no merge base ``` It is an orphan lineage, not a divergence. Its commits carry the earlier `coily` and `coilyco-ai` ancestry (`lockdown: regenerate from coily release`, `Sync catalog-block check from coilyco-ai canonical`), so it predates the history `main` grew from. That is why it cannot be diffed as a patch and why "reconcile" has to mean comparing behavior rather than comparing trees. Tip is `714d718`, 2026-07-28, and it is the 16-file refactor this issue names. ### What the retained refactor actually does Reading `714d718` rather than its subject line, the promotion is a **routing change**: * `Config.AgentProxyModel` becomes `Config.AgentProxyRoute` * the definition schema goes `sirens-discord-ops.agent.v2` to `v3` and gains `harness`, `role`, `intents`, and `default_intent` * `SIRENS_ECHO_INTENT` selects an intent, and `definition.LogicalRoute(intent)` derives the route from it * `AGENT_PROXY_MODEL` stops being required So model opacity is achieved there by having the definition declare a set of intents and computing a logical route from the selected one. ### Why it must not be merged That is role-intent routing, which #67 and #68 deliberately removed and which #76 records as the reason PR #77 is not a prerequisite for anything. Merging it would reintroduce the mechanism the profile architecture was built to replace. ### `main` already has the outcome, by a different mechanism The goal of the refactor was that the harness names no model. `main` satisfies that: * no tracked definition carries a model field at all, verified across `agent/*.yaml` * the route is `AGENT_PROXY_MODEL`, read from the environment at runtime, so the deployment owns it and the repository never states it * the definition schema is `coilyco-harness.agent.v1`, which has no model, intent, or route field to state one with `main` is model-opaque because a definition **cannot** name a model. The branch got there by letting the definition declare intents and derive a route. The stricter of the two is the one already shipped. ### Verdict The retained refactor is superseded, not lost. Its outcome is present on `main` and its mechanism is one the repository has since rejected on purpose. There is nothing to port. ### On deleting the branch I have not deleted it. Branch deletion is destructive and outside what I take on my own, and the tip is the only place that lineage exists. It is safe to delete on this analysis whenever you want it gone. Worth noting separately: eighteen other branches are still on the remote, several clearly merged. If a sweep is wanted that is its own issue rather than a side effect of this one.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
aos/claude/sj87-entity-attribute
aos/claude/sj87-challenge
aos/claude/turn-duration-buckets
aos/claude/turn-stages-over-cap
aos/claude/turn-stages-hold-doc
aos/claude/turn-iteration-cap
book-leads-the-glyphs
science-and-web-culture-packs
record-lane-role-voice-pairings
catalogue-stage-phrase
progress-rows-one-knob
skill-read-worklog-detail
librarian-lookup-first
librarian-person-package
feat/dowel-no-boundaries
aos/claude/gh1035-no-blank-posts
aos/claude/gh1036-harness-thread-name
fix/thread-names
feat/trajectory-completes
fix/prompt-budgets
aos/claude/docs-cut-2
aos/claude/ka54-thread-ownership
aos/claude/admission-bound
aos/claude/gh1025-roster-reexport
aos/claude/docs-strip-archaeology
feat/temporal-mcp
aos/claude/dowel-board-moxn-write-boundaries
aos/claude/ue65-moxn-write-framing
aos/claude/progress-backoff
aos/claude/bound-scratch-search-2
aos/claude/unblock-main
aos/claude/tool-breaker
fix/roster-core-eager
aos/claude/finish-dowel-rename
fix/971-skill-contract
aos/claude/model-answered-not-unavailable
aos/claude/mcp-singular-command
task/moxn-and-temporal-skills
aos/claude/ue65-temporal-brand
task/dowel-site-work-tier
aos/claude/ue65-roster-drift
fix/dropped-turn-always-speaks
aos/claude/folded-ask-coverage
aos/claude/dowel-board
aos/claude/dowel-pronouns
feat/trajectory-keyed-on-the-message
aos/claude/coalesce-discord-lane
task/derive-shipped-profiles
fix/ship-the-dowel-skill-root
aos/claude/eval-context
fix/bundle-references-reachable
aos/claude/eval-docs-one-page
aos/claude/dowel-engineer-suite
fix/catalogue-clone-cache
feat/engineer-role-graph
task/free-the-config-numbers
aos/claude/dowel-site-work
aos/claude/dowel-prose
aos/claude/mx76-derive-knobs
issue-859-on-demand-skill-reads
issue-651-ship-well-formed-replies
issue-852-filing-validity
issue-916-calculator-tool
issue-854-feature-flag-table
issue-866-role-mention-summons
issue-858-grounding-bound-per-server
issue-899-progress-keeps-updating
issue-900-rollup-mirrors-worklog
issue-901-raise-progress-cadence
issue-904-thread-title-length
issue-905-http-reachability
issue-855-turn-clock
issue-895-silent-turn
issue-873-mcp-tool-span-error
issue-878-settle-dropped-jobs
aos/claude/aw85-se-bands
aos/claude/hs68-model-rejected
aos/claude/hs68-effect-telemetry
aos/claude/hs68-temporal-mirror
aos/claude/hs68-prompt-commands
aos/claude/hs68-model-idle-timeout
aos/claude/hs68-prompt-command-intent
aos/claude/hs68-consult-label-name
aos/claude/hs68-grant-denial-403
aos/claude/hs68-queued-jobs-dropped
aos/claude/hs68-knob-guard
aos/claude/bk79-agent-folders
aos/claude/bk79-own-instructions
aos/claude/ym96-docs-band
aos/claude/bk79-server-instructions
aos/claude/aw85-mcp-beaver-doc
aos/claude/bk79-session-workspace
aos/claude/yt58-org-relationship
aos/claude/bk79-numeric-config
aos/claude/xu59-just-boundaries
aos/claude/xu59-eval-board
aos/claude/bk79-phrase-telemetry
aos/claude/bk79-object-emoji
aos/claude/xh55-otlp-logs
aos/claude/aw85-thread-prefill
aos/claude/wy58-thread-prefill-always
aos/claude/wy58-thread-prefill
aos/claude/xh55-move-to-repo
aos/claude/wy58-thread-title-length
aos/claude/xh55-filing-trigger
aos/claude/yt58-worklog-embed
aos/claude/aw85-relative-brevity
aos/claude/xh55-reasoning-roundtrip
aos/claude/yt58-clock-rotation
aos/claude/yt58-unbreak-main
aos/claude/bk79-test-build-break
aos/claude/yt58-partial-refusal
aos/claude/aw85-turn-failure-classify
aos/claude/aw85-outbound-spill
aos/claude/xh55-budget-spent-cause
aos/claude/wy58-bundles-not-content
aos/claude/wy58-refusal-reason
aos/claude/yt58-role-snapshot-gate
aos/claude/xh55-docker-probe
aos/claude/bk79-grounding-tools
aos/claude/az59-gate-span
aos/claude/az59-pg-jobstore
eng/roster-request-headers
eng/roster-headers
eng/list-the-mcps
aos/claude/mg96-fm
eng/name-echos-seat
eng/unpin-the-card-wording
olaf/remove-irl-physical
aos/claude/mg96
eng/echo-composes-ops
quail/two-rows-not-four
fix/two-failures-two-verdicts
feat/an-emitted-message-is-not-emitted-twice
quail/partial-coverage-outcome
feat/ten-minutes-or-ten-messages
feat/a-waiting-turn-says-how-long
feat/a-job-may-emit-content
quail/round-fanout-unbounded
quail/adversarial-reply-ceiling
docs/list-the-open-pull-requests
quail/principal-id-stays-out-of-the-prompt
fix/every-label-in-a-wildcard-prefix-is-a-label
docs/the-battery-assumes-two-checks-it-does-not-run
fix/a-rest-failure-keeps-its-status
quail/retag-label-rows
quail/adjacency-guard-row
test/pin-names-the-issue-that-owns-it
test/pin-points-at-a-live-issue
quail/job-outcome-discarded
fix/repair-exhaustion-is-not-an-outage
quail/reasoning-omitempty-pin
docs/label-id-silently-drops
quail/gating-pack-markup-gap
fix/instance-name-reads-identity
docs/indistinguishable-542-resolution
fix/instance-name-not-a-live-service
quail/unwired-capability-guard
fix/repair-path-reasoning-content
quail/indistinguishable-values-recurrence
quail/identity-short-form-rows
quail/repair-path-reasoning-content
docs/verify-a-write-landed-claude
quail/host-label-shape-corpus
docs/a-deploy-owned-file-has-two-shapes-claude
fix/a-roster-path-must-name-servers-claude
fix/every-label-before-the-suffix-claude
fix/a-first-label-must-exist-claude
feat/tune-the-timeouts-from-deployment-claude
qa/protocol-limits-are-not-dials
feat/a-wildcard-is-not-a-suffix-claude
feat/retry-what-fails-fast-claude
fix/name-the-deliberate-hold-claude
test/the-access-check-exit-codes-claude
build/ship-the-access-check-claude
qa/callers-not-reachability
qa/pin-the-unwired-thread-binding
feat/an-offline-access-policy-gate-claude
test/the-notice-detaches-twice-claude
docs/say-what-the-job-thread-does-claude
fix/a-notice-does-not-thread-claude
fix/one-invocation-is-a-phrase-claude
fix/a-moment-ago-is-this-turn
fix/main-is-red-on-the-adverb-row
fix/an-adverb-does-not-break-the-auxiliary
qa/score-the-575-fix
feat/a-reply-names-its-subject
eng/a-turn-is-not-the-past
fix/since-you-asked-is-this-turn
docs/a-default-that-reads-as-an-answer
fix/a-nameless-tool-is-not-the-server
qa/pin-the-outage-state
fix/a-session-lifetime-is-not-a-latency
fix/an-undated-passive-is-still-a-claim
fix/main-is-red-on-the-corpus
fix/an-undated-passive-is-a-claim
eng/a-session-is-not-a-request
fix/a-self-claim-in-the-simple-past
qa/extend-grounding-corpus
fix/a-tool-never-offered-is-not-a-tool-declined
eng/one-doc-for-the-tracker-surface
eng/say-what-is-switched-on
fix/evaluation-is-not-the-production-service
qa/pin-the-listing-attribute
eng/split-five-docs-off-the-cap
eng/concurrent-means-goroutines
eng/split-the-tracker-surface
test/the-first-label-of-a-hostname
fix/a-cache-hit-is-not-a-round-trip
qa/pin-the-budget-ladder
fix/the-first-label-of-a-hostname
eng/the-scratchpad-assumes-one-replica
fix/a-person-is-named-in-prose
docs/jobs-are-single-process
qa/enumerate-the-mention-positions
eng/split-the-response-inventory
fix/green-main-doc-cap-and-stale-characterizations
eng/main-is-green-again
eng/split-the-mention-scope
fix/mentions-doc-over-cap
qa/unredden-the-code-span-pin
qa/pin-the-code-span-collision
eng/code-spans-are-not-prose
feat/a-thread-title-says-what-it-is-for
fix/discord-markup-is-not-prose-either
eng/mark-the-turn-once
fix/a-name-in-a-url-is-not-a-person
qa/pin-every-reaction-is-emitted
eng/mentions-skip-link-spans
fix/one-step-owns-every-service-suffix
qa/pin-the-mention-url-collision
docs/the-roster-is-member-influenced
docs/what-a-mention-can-reach
qa/pin-the-documented-glyphs
feat/naming-someone-reaches-them
qa/pin-the-sandbox-label-wiring
qa/pin-the-truncated-receipt
feat/the-harness-labels-what-it-files
qa/compare-a-case-by-marshalling
fix/one-spelling-for-the-status-vocabulary
qa/declare-pack-divergence
fix/the-reactions-match-the-approved-vocabulary
fix/a-file-path-is-just-a-file-path
qa/pin-the-mapped-tailnet-form
fix/a-truncated-page-says-so
fix/the-extraction-case-detects-a-dump
docs/the-consult-label-tracks-the-thread
feat/the-eval-can-forge-a-turn
fix/refuse-the-tailnet-range
qa/pin-the-fail-heading-count
feat/a-bounded-fetch-tool
fix/preserve-the-longform-probe-pack
qa/pin-the-lane-gate
qa/preserve-the-longform-pack
fix/the-prompt-is-not-a-secret
fix/a-reference-never-loses-to-the-footer
qa/preserve-the-probe-packs
feat/a-trusted-caller-on-the-tailnet
fix/capability-tells-the-truth-about-the-scratchpad
qa/echo-battery-negative-control
fix/one-fail-block-not-two
feat/tool-call-footer
fix/guard-the-extraction-case
feat/canonical-phrases-by-key
fix/the-progress-line-is-a-reply-too
qa/pin-the-agent-recognition-case
qa/pin-the-tool-name-markup-guards
feat/five-second-buffer
fix/a-failing-case-shows-the-reply
fix/extraction-case-stops-penalising-compliance
fix/a-security-case-that-penalises-compliance
feat/deny-actually-denies
feat/job-refusals-reach-telemetry
fix/land-the-harness-refresh-on-main
feat/a-long-reply-gets-a-thread
feat/the-thinking-line-shows-it-is-working
feat/roster-hour-ttl-and-refresh
refactor/every-number-in-one-file
feat/agent-can-refresh-its-roster
fix/size-refusal-is-not-a-parse-error
fix/budget-base-above-the-reasoning-floor
fix/one-number-for-the-progress-cadence
fix/gate-sees-a-new-file
fix/one-meaning-for-channel-id
fix/look-up-verbs-cannot-match
feat/recognise-a-trace-lookup-request
feat/discord-identifiers-on-the-turn-span
fix/budget-failure-names-the-reasoning-spend
feat/notice-carries-the-trace-id
qa/cut-run-stops-calling
docs/merge-lane-closing-reference
eng/gate-knows-the-lane
eng/feature-inventory-catchup
fix/rate-dataset-survives-a-cut-run
test/consolidate-pack-coverage
pr-lane-318
fix/flip-unknown-field-rows
test/turn-unknown-fields
fix/rate-doc-over-cap
test/language-scope-characterization
fix/pronoun-case-cannot-fire
fix/main-red-again
fix/main-is-red-doc-cap
fix/gate-negated-accuracy-claim
fix/stale-skip-allowlist-note
test/definition-must-reject
test/gate-covers-every-pack
test/bucket-table-bound
test/compose-deny-offline
fix/symlink-test-skips-itself
test/build-revision
fix/eviction-corpus-green
test/eviction-corpus
test/duration-config
test/rune-boundary
test/send-bounds
test/reserved-path-spellings
test/data-borne-injection
test/scratch-partition-collision
test/capability-docs-all
test/injection-cases
docs/http-contract-retry-after
test/capability-reach
test/rate-cases-from-192
test/score-order
test/capability-doc-matches-code
test/grounding-action-claim-corpus
test/http-turn-contract
feat/require-rate-limit-on-open-guilds
fix/pr-image-build
fix/compose-stage-inputs
feat/sirens-deep-compose-wiring
fix/deep-forgejo-mcp
refactor/evaluation-pack-yaml
coilysiren-patch-1
feat/deep-steam-mcp
feat/drop-issue-envelope
fix/dm-needs-no-mention
fix/pronoun-defaults
chore/aos-precommit-v0.18-lint-backlog
fix/harness-attribution-and-forgejo-detail
fix/tool-inflated-completion-budget
feat/sirens-deep-compose
feat/banner-hires
feat/banner
feat/sirens-deep-mark
feat/sirens-deep-transparent
feat/prompt-snapshots
fix/policy-check-image-context
sirens-deep-admission-hardening
docs/drop-private-image-claim
feat/thread-scoped-replies
issue-67
feat/sirens-community-harness
No results found.
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#73
No description provided.