coilyco-gaming/eco-app
Watch
2
0
Code Issues 33 Pull requests Projects Releases Packages 1 Wiki Activity Actions

Implement single-owner DiscordLink preview parity with rich Eco embeds #144

New issue
Open
opened 2026-07-23 04:09:13 +00:00 by coilyco-ops · 9 comments
coilyco-ops commented 2026-07-23 04:09:13 +00:00
Member
Copy link

Direction

Implement the DiscordLink preview replacement as one cohesive workstream. Do not split commands, embed types, or the parity inventory across sibling implementation runs.

The authoritative design is #143 and docs/discord-bot.md. This is an implementation child of the DiscordLink retirement epic #37.

Scope

  1. Inventory every read-only preview or embed that the active Sirens DiscordLink configuration currently exposes. Record a parity matrix in the issue or a tracked document. Chat sync stays and is not part of this replacement.
  2. Implement the rich slash-command worker described by #143: Pycord, async eco-app HTTP client, shared typed embed factory, explicit command registration, bounded timeouts, structured logs, and no privileged intents.
  3. Ship the five specified commands: /eco status, /eco world, /eco economy, /eco player <name>, and /eco help.
  4. Extend that command set inside this same workstream until every currently active DiscordLink read-only preview has a rich Eco equivalent. Reuse public /preview*.json data planes. Add a missing public-safe data plane only when parity requires it. Do not call the game server around eco-app.
  5. Ensure every success, degraded, empty, timeout, and error response is exactly one branded embed with no plain-text success fallback. Enforce all Discord limits before delivery and link each result to its canonical SPA page.
  6. Publish documented web, Discord-worker, and command-registration entrypoints in the existing eco-app image.
  7. Update coilyco-bridge/deploy with a separate one-replica Discord worker Deployment and ExternalSecret wiring. Keep tokens and opaque identifiers in SSM only.
  8. Update the active DiscordLink configuration in coilyco-gaming/eco-ops only after equivalent rich commands exist, leaving chat sync enabled.
  9. Update docs/FEATURES.md and operator documentation in every affected repo.

Safety and rollout

Register commands in a test guild first. Do not globally register commands or disable a DiscordLink surface until live parity is verified. The implementation may leave those final externally visible actions as an explicit director or ops checkpoint, as required by #143.

Do not implement ordinary-message parsing, automatic URL unfurls, mutations, moderation, direct messages, scheduled posts, trade-watch notifications, sharding, or multiple guild configurations.

Tests and acceptance

  • Every active DiscordLink read-only preview appears in the recorded parity matrix and has a rich Eco replacement or an explicit human-blocked checkpoint.
  • Each command maps to the intended eco-app endpoint and canonical SPA URL.
  • Mocked interaction tests prove deferral happens before upstream work and every path resolves exactly one embed.
  • Embed limits, long values, markup, mentions, redaction, timeouts, malformed upstream responses, and unexpected failures are covered.
  • Worker startup never registers commands and requests no privileged intents.
  • ward exec test, ward exec lint, ward exec smoke, and ward exec precommit pass in eco-app.
  • The deploy change validates through that repo gates.
  • Both repositories land their required commits. The issue records any live registration or DiscordLink-disable checkpoint still requiring director or ops action.
## Direction Implement the DiscordLink preview replacement as one cohesive workstream. Do not split commands, embed types, or the parity inventory across sibling implementation runs. The authoritative design is #143 and `docs/discord-bot.md`. This is an implementation child of the DiscordLink retirement epic #37. ## Scope 1. Inventory every read-only preview or embed that the active Sirens DiscordLink configuration currently exposes. Record a parity matrix in the issue or a tracked document. Chat sync stays and is not part of this replacement. 2. Implement the rich slash-command worker described by #143: Pycord, async eco-app HTTP client, shared typed embed factory, explicit command registration, bounded timeouts, structured logs, and no privileged intents. 3. Ship the five specified commands: `/eco status`, `/eco world`, `/eco economy`, `/eco player <name>`, and `/eco help`. 4. Extend that command set inside this same workstream until every currently active DiscordLink read-only preview has a rich Eco equivalent. Reuse public `/preview*.json` data planes. Add a missing public-safe data plane only when parity requires it. Do not call the game server around eco-app. 5. Ensure every success, degraded, empty, timeout, and error response is exactly one branded embed with no plain-text success fallback. Enforce all Discord limits before delivery and link each result to its canonical SPA page. 6. Publish documented web, Discord-worker, and command-registration entrypoints in the existing eco-app image. 7. Update `coilyco-bridge/deploy` with a separate one-replica Discord worker Deployment and ExternalSecret wiring. Keep tokens and opaque identifiers in SSM only. 8. Update the active DiscordLink configuration in `coilyco-gaming/eco-ops` only after equivalent rich commands exist, leaving chat sync enabled. 9. Update `docs/FEATURES.md` and operator documentation in every affected repo. ## Safety and rollout Register commands in a test guild first. Do not globally register commands or disable a DiscordLink surface until live parity is verified. The implementation may leave those final externally visible actions as an explicit director or ops checkpoint, as required by #143. Do not implement ordinary-message parsing, automatic URL unfurls, mutations, moderation, direct messages, scheduled posts, trade-watch notifications, sharding, or multiple guild configurations. ## Tests and acceptance - Every active DiscordLink read-only preview appears in the recorded parity matrix and has a rich Eco replacement or an explicit human-blocked checkpoint. - Each command maps to the intended eco-app endpoint and canonical SPA URL. - Mocked interaction tests prove deferral happens before upstream work and every path resolves exactly one embed. - Embed limits, long values, markup, mentions, redaction, timeouts, malformed upstream responses, and unexpected failures are covered. - Worker startup never registers commands and requests no privileged intents. - `ward exec test`, `ward exec lint`, `ward exec smoke`, and `ward exec precommit` pass in eco-app. - The deploy change validates through that repo gates. - Both repositories land their required commits. The issue records any live registration or DiscordLink-disable checkpoint still requiring director or ops action.
coilyco-ops commented 2026-07-23 04:21:32 +00:00
Author
Member
Copy link

WARDED_WORKFLOW: done ✅

details

review summary: implemented and landed; in-container review gate intentionally skipped because the temporary ward default is pending brokered QA.

workflow: merge-remote-main; review summary: gate skipped per temporary ward default, validation and commit hooks completed where available.

Felt: cohesive and bounded; the shared embed contract kept the command paths simple.

Confidence: high for implementation and manifest wiring; live Discord behavior remains unverified by design.

Surprises: both remote mains advanced during landing, so each branch was rebased and freshly verified after push; the deploy render gate lacks envsubst, and eco-app precommit-all is blocked by an unrelated existing Ruff naming error.

Follow-ups: operator registers in the test guild and verifies live parity; do not globally register or disable DiscordLink. The active work-party display still needs an approved public-safe eco-app data plane; chat sync remains enabled.

WARDED_WORKFLOW: done ✅ <details><summary>details</summary> review summary: implemented and landed; in-container review gate intentionally skipped because the temporary ward default is pending brokered QA. workflow: merge-remote-main; review summary: gate skipped per temporary ward default, validation and commit hooks completed where available. Felt: cohesive and bounded; the shared embed contract kept the command paths simple. Confidence: high for implementation and manifest wiring; live Discord behavior remains unverified by design. Surprises: both remote mains advanced during landing, so each branch was rebased and freshly verified after push; the deploy render gate lacks envsubst, and eco-app precommit-all is blocked by an unrelated existing Ruff naming error. Follow-ups: operator registers in the test guild and verifies live parity; do not globally register or disable DiscordLink. The active work-party display still needs an approved public-safe eco-app data plane; chat sync remains enabled. </details>
coilyco-ops commented 2026-07-23 04:21:40 +00:00
Author
Member
Copy link

WARDED_WORKFLOW: blocked 🛑

salvage details

An ephemeral ward container (codex mode) dispatched for this issue finished but its work was not merged to main, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for #144 never reached main). Recover from the salvage branch below.

  • Repo: coilyco-gaming/eco-app
  • Salvage branch: ward-salvage/eco-app-b8207ef3
  • Pull request: not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input
  • Reason: merge conflict integrating onto main
  • Container uptime at reap: 11m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Cleanup diagnostics

--- reap diagnostics ---
ward version:      v0.788.0
version source:    pinned via WARD_VERSION/--ward-version (v0.788.0)
HEAD:              9daa7d0f74bb
origin/main:       9daa7d0f74bb
ancestry:          HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature)
decision gate:     provenance missing or unreadable on already-landed merge-remote-main run
reason:            merge conflict integrating onto main
provenance:        missing or unreadable
run-owned landed:  no
working tree:      clean
container uptime:  11m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-gaming/eco-app.git ward-salvage/eco-app-b8207ef3
git checkout -b ward-salvage/eco-app-b8207ef3 FETCH_HEAD

— Codex, via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>salvage details</summary> An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for #144 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-gaming/eco-app` - **Salvage branch:** `ward-salvage/eco-app-b8207ef3` - **Pull request:** not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input - **Reason:** merge conflict integrating onto main - **Container uptime at reap:** 11m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Cleanup diagnostics ``` --- reap diagnostics --- ward version: v0.788.0 version source: pinned via WARD_VERSION/--ward-version (v0.788.0) HEAD: 9daa7d0f74bb origin/main: 9daa7d0f74bb ancestry: HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature) decision gate: provenance missing or unreadable on already-landed merge-remote-main run reason: merge conflict integrating onto main provenance: missing or unreadable run-owned landed: no working tree: clean container uptime: 11m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-gaming/eco-app.git ward-salvage/eco-app-b8207ef3 git checkout -b ward-salvage/eco-app-b8207ef3 FETCH_HEAD ``` </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-23 04:21:45 +00:00
Author
Member
Copy link

WARDED_WORKFLOW: reopened

grant details

This run held --repo grants and closed against coilyco-gaming/eco-app, but cleanup could not confirm every granted repo's work reached its main. A secondary push can be silently rejected (a non-fast-forward on a busy main, a dead/rotated PAT) while the primary push succeeds, so the issue is reopened rather than left reading "done" with the cross-repo half lost.

coilyco-gaming/eco-ops

  • Verdict: 1 local commit(s) never reached origin/main.
  • Preserved on: ward-salvage/eco-ops-7227a5b2
git fetch https://forgejo.coilysiren.me/coilyco-gaming/eco-ops.git ward-salvage/eco-ops-7227a5b2
git checkout -b ward-salvage/eco-ops-7227a5b2 FETCH_HEAD

Re-run the cross-repo half, or - per ward#291 - file it as a native issue in the granted repo so it becomes a single-repo run that sidesteps this failure mode.

— Codex, via ward agent

WARDED_WORKFLOW: reopened <details><summary>grant details</summary> This run held `--repo` grants and closed against `coilyco-gaming/eco-app`, but cleanup could not confirm every granted repo's work reached its `main`. A secondary push can be silently rejected (a non-fast-forward on a busy `main`, a dead/rotated PAT) while the primary push succeeds, so the issue is **reopened** rather than left reading "done" with the cross-repo half lost. ### `coilyco-gaming/eco-ops` - **Verdict:** 1 local commit(s) never reached `origin/main`. - **Preserved on:** `ward-salvage/eco-ops-7227a5b2` ```bash git fetch https://forgejo.coilysiren.me/coilyco-gaming/eco-ops.git ward-salvage/eco-ops-7227a5b2 git checkout -b ward-salvage/eco-ops-7227a5b2 FETCH_HEAD ``` Re-run the cross-repo half, or - per ward#291 - file it as a native issue in the granted repo so it becomes a single-repo run that sidesteps this failure mode. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-23 04:21:46 +00:00
Author
Member
Copy link

WARDED_WORKFLOW: reservation-released

release details

Run finished with WARDED_WORKFLOW: blocked 🛑.

ward container reap released container engineer-codex-eco-app-144 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

<!-- ward-agent-reservation-released --> WARDED_WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARDED_WORKFLOW: blocked 🛑`. `ward container reap` released container `engineer-codex-eco-app-144` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-23 05:07:18 +00:00
Author
Member
Copy link

Live operator checkpoint, 2026-07-23: build-publish run 10007 (#113) is green on 9daa7d0; deploy validation run 10012 and Eco rollout run 10013 are green on deploy main 26d57ea. The app is live on 9daa7d0 and the new detailedTrades/rollupRows/rollupTrades data is present. The three Discord SSM parameters were absent; they were seeded from the authenticated live DiscordLink bot/config without exposing values, the ExternalSecret now reports SecretSynced/Ready, and the worker is 1/1 Available with a connected Discord gateway. eco-discord-register was run test-guild-only and the REST readback confirms exactly /eco {status, world, economy, player, help}. No global registration occurred and DiscordLink remains unchanged. Final parity is not yet green: a live worker probe found /preview/currency.json returning 500 because its payload contains inf, which breaks /eco economy. Captured and dispatched as eco-app#147. The already-documented work-party public-safe data-plane checkpoint also remains.

Live operator checkpoint, 2026-07-23: build-publish run 10007 (#113) is green on 9daa7d0; deploy validation run 10012 and Eco rollout run 10013 are green on deploy main 26d57ea. The app is live on 9daa7d0 and the new detailedTrades/rollupRows/rollupTrades data is present. The three Discord SSM parameters were absent; they were seeded from the authenticated live DiscordLink bot/config without exposing values, the ExternalSecret now reports SecretSynced/Ready, and the worker is 1/1 Available with a connected Discord gateway. `eco-discord-register` was run test-guild-only and the REST readback confirms exactly /eco {status, world, economy, player, help}. No global registration occurred and DiscordLink remains unchanged. Final parity is not yet green: a live worker probe found /preview/currency.json returning 500 because its payload contains inf, which breaks /eco economy. Captured and dispatched as eco-app#147. The already-documented work-party public-safe data-plane checkpoint also remains.
coilyco-ops commented 2026-07-23 05:24:12 +00:00
Author
Member
Copy link

WARDED_WORKFLOW: blocked 🛑

details

human comment by @coilyco-ops at 2026-07-23T05:07:18Z is newer than the latest ward acknowledgement at 2026-07-23T04:21:46Z

This action is blocked until the feedback is visibly acknowledged.

— Codex, via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> human comment by @coilyco-ops at 2026-07-23T05:07:18Z is newer than the latest ward acknowledgement at 2026-07-23T04:21:46Z This action is blocked until the feedback is visibly acknowledged. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-23 05:24:24 +00:00
Author
Member
Copy link

Acknowledged the live operator checkpoint and the remaining parity blockers. PR #145 is only a false-salvage duplicate whose head is already on main; closing that PR does not close this issue or waive the currency/work-party/live-verification checkpoints.

Acknowledged the live operator checkpoint and the remaining parity blockers. PR #145 is only a false-salvage duplicate whose head is already on main; closing that PR does not close this issue or waive the currency/work-party/live-verification checkpoints.
coilyco-ops commented 2026-07-23 05:24:25 +00:00
Author
Member
Copy link

WARDED_WORKFLOW: blocked 🛑

details

human comment by @coilyco-ops at 2026-07-23T05:24:24Z is newer than the latest ward acknowledgement at 2026-07-23T05:24:12Z

This action is blocked until the feedback is visibly acknowledged.

— Codex, via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> human comment by @coilyco-ops at 2026-07-23T05:24:24Z is newer than the latest ward acknowledgement at 2026-07-23T05:24:12Z This action is blocked until the feedback is visibly acknowledged. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-26 00:28:13 +00:00
Author
Member
Copy link

Current checkpoint after the earlier ward acknowledgement loop:

  • The core implementation and deploy wiring remain live. Both the app and Discord worker are 1/1 Available on current eco-app main.
  • #147 is closed and the live currency preview returns strict JSON, so the former /eco economy blocker is gone.
  • #148 changed the command contract after the first guild registration. The current schema is /eco rich {status, world, economy, player, help} scoped to #eco-app, so the operator must re-run test-guild registration and verify that exact schema before any global action.
  • No work-party data plane exists in the repository. The operator must capture the active DiscordLink exporter headers and example field shapes without posting player data. The director then approves which fields are public-safe. Only then can an engineer add the final parity command.
  • Global registration and DiscordLink display retirement remain forbidden until the work-party replacement and live command pass are both recorded. Chat sync stays.

The next code step is blocked only on the public-safe work-party contract. The next live step is the updated test-guild registration and five-command verification.

Current checkpoint after the earlier ward acknowledgement loop: * The core implementation and deploy wiring remain live. Both the app and Discord worker are `1/1` Available on current eco-app `main`. * #147 is closed and the live currency preview returns strict JSON, so the former `/eco economy` blocker is gone. * #148 changed the command contract after the first guild registration. The current schema is `/eco rich {status, world, economy, player, help}` scoped to `#eco-app`, so the operator must re-run test-guild registration and verify that exact schema before any global action. * No work-party data plane exists in the repository. The operator must capture the active DiscordLink exporter headers and example field shapes without posting player data. The director then approves which fields are public-safe. Only then can an engineer add the final parity command. * Global registration and DiscordLink display retirement remain forbidden until the work-party replacement and live command pass are both recorded. Chat sync stays. The next code step is blocked only on the public-safe work-party contract. The next live step is the updated test-guild registration and five-command verification.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
aos/claude/bk79-eco-pr-ci
aos/claude/bk79-eco-instructions
aos/claude/mg96-fm
aos/claude/mg96
feat/autogen-recipe-index
recovery/2026-07-27-local-work
ward-salvage/eco-app-84ad1890
ward-salvage/eco-app-b3384b9b
ward-salvage/eco-app-0c6e4df2
ward-salvage/eco-app-b8207ef3
ward-salvage/eco-app-a58b14ad
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
headless
Safe for autonomous warded engineer carry

  
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
burndown-2026-06
headless
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/eco-app#144
No description provided.