coordination: team and agent channel (decisions, handoffs, blockers) #40

Open
opened 2026-11-15 22:27:46 -05:00 by forgejo_admin · 14 comments
Owner

The shared channel for the team and its coding agents. Every agent reads the comments here at the start of each session and again before opening a pull request (CLAUDE.md, first section).

PLAN.md is a starting point, not a contract. When a different decision makes dongba more robust, simpler or faster, propose it here instead of quietly diverging.

Posting — start each comment with one tag:

Tag Use
[PROPOSAL] A design change: context, proposal, impact on other areas, affected issues. Mention whoever it affects
[DECISION] Outcome of a proposal, posted after the affected people agreed (a 👍 counts). The proposer then updates PLAN.md/docs and the affected issues
[HANDOFF] Something another member's work can now use (endpoint merged, contract changed, schema changed)
[BLOCKED] Work stopped waiting on someone; link the issue
[FYI] Anything else the team should know

Rules

  • Contract changes (openapi.yaml, db/) always get a [HANDOFF] here when merged
  • Agents sign their comments with the member they work for, e.g. — agent for @liam
  • Agents never decide alone on a change that alters another member's area: they post a [PROPOSAL] and continue with work that does not depend on it
  • Keep each comment self-contained; link issues and PRs by number
  • This issue never closes
The shared channel for the team **and its coding agents**. Every agent reads the comments here at the start of each session and again before opening a pull request (CLAUDE.md, first section). PLAN.md is a starting point, not a contract. When a different decision makes dongba more robust, simpler or faster, propose it here instead of quietly diverging. **Posting** — start each comment with one tag: | Tag | Use | | --- | --- | | `[PROPOSAL]` | A design change: context, proposal, impact on other areas, affected issues. Mention whoever it affects | | `[DECISION]` | Outcome of a proposal, posted after the affected people agreed (a 👍 counts). The proposer then updates PLAN.md/docs and the affected issues | | `[HANDOFF]` | Something another member's work can now use (endpoint merged, contract changed, schema changed) | | `[BLOCKED]` | Work stopped waiting on someone; link the issue | | `[FYI]` | Anything else the team should know | **Rules** - Contract changes (`openapi.yaml`, `db/`) always get a `[HANDOFF]` here when merged - Agents sign their comments with the member they work for, e.g. `— agent for @liam` - Agents never decide alone on a change that alters another member's area: they post a `[PROPOSAL]` and continue with work that does not depend on it - Keep each comment self-contained; link issues and PRs by number - This issue never closes
Author
Owner

[FYI] Board bootstrap done: issues #1–#39 with milestones, dependencies and status/* labels. Schema is live on the server (dongba empty, dongba_test with demo data). @liam can start with #5 and #6, @felipe_bhrqz with #8 and #9 in parallel.

— agent for @yuuhikaze

[FYI] Board bootstrap done: issues #1–#39 with milestones, dependencies and `status/*` labels. Schema is live on the server (`dongba` empty, `dongba_test` with demo data). @liam can start with #5 and #6, @felipe_bhrqz with #8 and #9 in parallel. — agent for @yuuhikaze
Author
Owner

[HANDOFF] Platform access for maintainers is in place.

  • Keycloak (internal realm): the groups k8s_dongba_maintainer / k8s_dongba_viewer exist. @felipe_bhrqz, @liam and @yuuhikaze are in the maintainer group.
  • OpenBao (https://vault.yhkze.net): maintainers read and write the dongba/ mount. Sign out and back in to pick up the group.
    • dongba/mariadb-test and dongba/mariadb-prod hold the app credentials consumed by k8s.
    • dongba/staff/liam holds Liam's personal DB password. @liam: copy it to your password manager and say so here; it gets deleted afterwards. OpenBao keeps only what k8s consumes.
  • ArgoCD (https://argocd.yhkze.net): maintainers can get, sync and run actions on dongba-* applications (they appear once deployed).
  • Kargo: maintainers can sign in. Promotion rights on the dongba project come with its promotion manifest.
  • Perses (https://hari.yhkze.net): the dongba project is committed and goes live with the next server rebuild.

— agent for @yuuhikaze

[HANDOFF] Platform access for maintainers is in place. - Keycloak (internal realm): the groups `k8s_dongba_maintainer` / `k8s_dongba_viewer` exist. @felipe_bhrqz, @liam and @yuuhikaze are in the maintainer group. - **OpenBao** (<https://vault.yhkze.net>): maintainers read and write the `dongba/` mount. Sign out and back in to pick up the group. - `dongba/mariadb-test` and `dongba/mariadb-prod` hold the app credentials consumed by k8s. - `dongba/staff/liam` holds Liam's personal DB password. **@liam: copy it to your password manager and say so here; it gets deleted afterwards.** OpenBao keeps only what k8s consumes. - **ArgoCD** (<https://argocd.yhkze.net>): maintainers can get, sync and run actions on `dongba-*` applications (they appear once deployed). - **Kargo**: maintainers can sign in. Promotion rights on the dongba project come with its promotion manifest. - **Perses** (<https://hari.yhkze.net>): the dongba project is committed and goes live with the next server rebuild. — agent for @yuuhikaze
Author
Owner

[HANDOFF] PR #41 is merged: master now has CLAUDE.md, PLAN.md, db/, openapi.yaml and the docs. Pull before starting. @felipe_bhrqz can take #8 and #9, @liam #5, #6 and #7.

— agent for @yuuhikaze

[HANDOFF] PR #41 is merged: `master` now has CLAUDE.md, PLAN.md, `db/`, `openapi.yaml` and the docs. Pull before starting. @felipe_bhrqz can take #8 and #9, @liam #5, #6 and #7. — agent for @yuuhikaze
Collaborator

[FYI] Heads up, three changes:

  1. master was force-pushed once to scrub a revoked token from history. If you cloned before now: git fetch && git checkout master && git reset --hard origin/master (nothing of yours was on master yet).
  2. Merges are rebase-only and branches are deleted on merge. Keep each branch commit a clean Angular commit (git rebase -i master on your own branch before review).
  3. Board: https://git.yhkze.net/k8s-services/dongba/projects/2. Agents move cards with scripts/board.sh <issue> <status>, using the bot token and password from OpenBao (dongba/forgejo-token, dongba/forgejo-web). Run bao login -method=oidc first. CLAUDE.md is updated; pull it.

— agent for @yuuhikaze

[FYI] Heads up, three changes: 1. **master was force-pushed once** to scrub a revoked token from history. If you cloned before now: `git fetch && git checkout master && git reset --hard origin/master` (nothing of yours was on master yet). 2. **Merges are rebase-only** and branches are deleted on merge. Keep each branch commit a clean Angular commit (`git rebase -i master` on your own branch before review). 3. **Board**: <https://git.yhkze.net/k8s-services/dongba/projects/2>. Agents move cards with `scripts/board.sh <issue> <status>`, using the bot token and password from OpenBao (`dongba/forgejo-token`, `dongba/forgejo-web`). Run `bao login -method=oidc` first. CLAUDE.md is updated; pull it. — agent for @yuuhikaze
Author
Owner

[HANDOFF] The schema, contract and plan changed before kickoff (PRs #43, #44, #51). Pull master.

  • #1 is closed: the professor approved Keycloak. Users are keyed on the token sub (users.oidc_subject); identities is gone.
  • New tables: admin_actions (audit), account_deletions (termination queue: reason, email notice, 30-day grace, appeal), output_formats and backend_formats (PDF, HTML page or site, DOCX, ODT, EPUB, LaTeX, Typst, Markdown, PNG, SVG). Blobs gain encoding and stored_bytes. The count is now 19 core, 7 many-to-many, 8 dictionaries, 15 views, 37 procedures. dongba and dongba_test on the server were recreated from it.
  • New issues:
    • #45 storage pipeline (uploads compressed losslessly; images optimized by default, opt-out)
    • #46 admin API, #47 termination pipeline, #48 admin area for @felipe_bhrqz
    • #49 upload dialog with the optimize checkbox for @felipe_bhrqz
    • #50 review of the new procedures for @liam
  • @liam: run #5 (Workbench) against the new dongba_test; #6 gained the admin and termination cases.
  • Workers no longer use tern; #24 is now "worker toolchains and output profiles".

— agent for @yuuhikaze

[HANDOFF] The schema, contract and plan changed before kickoff (PRs #43, #44, #51). Pull master. - #1 is closed: the professor approved Keycloak. Users are keyed on the token `sub` (`users.oidc_subject`); `identities` is gone. - New tables: `admin_actions` (audit), `account_deletions` (termination queue: reason, email notice, 30-day grace, appeal), `output_formats` and `backend_formats` (PDF, HTML page or site, DOCX, ODT, EPUB, LaTeX, Typst, Markdown, PNG, SVG). Blobs gain `encoding` and `stored_bytes`. The count is now 19 core, 7 many-to-many, 8 dictionaries, 15 views, 37 procedures. `dongba` and `dongba_test` on the server were recreated from it. - New issues: - #45 storage pipeline (uploads compressed losslessly; images optimized by default, opt-out) - #46 admin API, #47 termination pipeline, #48 admin area for @felipe_bhrqz - #49 upload dialog with the optimize checkbox for @felipe_bhrqz - #50 review of the new procedures for @liam - @liam: run #5 (Workbench) against the new `dongba_test`; #6 gained the admin and termination cases. - Workers no longer use tern; #24 is now "worker toolchains and output profiles". — agent for @yuuhikaze
Collaborator

Who is blocking whom — kept current by scripts/watch.py every hour.

Issue Status Assignee Blocks Idle
#8 design: UI drafts for approval before styling ready @felipe_bhrqz #48, #30, #16, #15, #14 20 h
#11 backend: projects, files and tags API blocked @yuuhikaze #27, #25, #22, #13, #12 1 h
#16 web: editor shell blocked @felipe_bhrqz #49, #26, #23, #21, #17 1 h
#3 backend: cargo workspace and api skeleton ready @yuuhikaze #45, #10, #4 20 h
#6 db: test suite for routines, triggers and rollbacks ready @liam #50, #31, #19 20 h
#9 web: SvelteKit scaffold, i18n and typed API client ready @felipe_bhrqz #16, #15, #14 20 h
#10 backend: Keycloak token verification and sign-in blocked @yuuhikaze #46, #20, #11 1 h
#15 web: project dashboard blocked @felipe_bhrqz #48, #28, #18 1 h
#26 web: render pane blocked @felipe_bhrqz #55, #54, #34 1 h
#30 web: reports module blocked @felipe_bhrqz #55, #54, #36 1 h
#25 backend: render worker blocked @yuuhikaze #29, #26 1 h
#45 backend: storage pipeline (compression and image optimization) blocked @yuuhikaze #49, #11 1 h
#2 devops: CI workflow for rust, web and db ready @yuuhikaze #4 20 h
#5 db: reverse-engineer the schema in MySQL Workbench ready @liam #32 20 h
#7 db: schema migration convention ready @liam, @yuuhikaze #32 20 h
#14 web: sign-in flow and session blocked @felipe_bhrqz #33 13 h
#20 backend: real-time collaboration service blocked @yuuhikaze #21 13 h
#21 web: collaborative editing blocked @felipe_bhrqz #34 13 h
#22 backend: comments API blocked @yuuhikaze #23 13 h
#24 render: worker toolchains and output profiles ready @yuuhikaze #25 20 h
#27 backend: notifications and activity API blocked @yuuhikaze #28 13 h
#29 backend: reports API blocked @yuuhikaze #30 1 h
#31 db: demo dataset for the presentation blocked @liam #32 13 h
#32 deliverable: final SQL file and DER blocked @liam #35 13 h
#34 web: responsive, accessibility and regression pass blocked @felipe_bhrqz #54 1 h
#46 backend: admin API blocked @yuuhikaze #47 1 h
#48 web: admin area blocked @felipe_bhrqz #54 1 h
#54 qa: bug-fix round before the presentation blocked @yuuhikaze, @felipe_bhrqz, @liam #36 1 h
#55 devops: scripted demo recording tooling blocked @yuuhikaze #36 1 h
**Who is blocking whom** — kept current by scripts/watch.py every hour. | Issue | Status | Assignee | Blocks | Idle | | --- | --- | --- | --- | --- | | #8 design: UI drafts for approval before styling | ready | @felipe_bhrqz | #48, #30, #16, #15, #14 | 20 h | | #11 backend: projects, files and tags API | blocked | @yuuhikaze | #27, #25, #22, #13, #12 | 1 h | | #16 web: editor shell | blocked | @felipe_bhrqz | #49, #26, #23, #21, #17 | 1 h | | #3 backend: cargo workspace and api skeleton | ready | @yuuhikaze | #45, #10, #4 | 20 h | | #6 db: test suite for routines, triggers and rollbacks | ready | @liam | #50, #31, #19 | 20 h | | #9 web: SvelteKit scaffold, i18n and typed API client | ready | @felipe_bhrqz | #16, #15, #14 | 20 h | | #10 backend: Keycloak token verification and sign-in | blocked | @yuuhikaze | #46, #20, #11 | 1 h | | #15 web: project dashboard | blocked | @felipe_bhrqz | #48, #28, #18 | 1 h | | #26 web: render pane | blocked | @felipe_bhrqz | #55, #54, #34 | 1 h | | #30 web: reports module | blocked | @felipe_bhrqz | #55, #54, #36 | 1 h | | #25 backend: render worker | blocked | @yuuhikaze | #29, #26 | 1 h | | #45 backend: storage pipeline (compression and image optimization) | blocked | @yuuhikaze | #49, #11 | 1 h | | #2 devops: CI workflow for rust, web and db | ready | @yuuhikaze | #4 | 20 h | | #5 db: reverse-engineer the schema in MySQL Workbench | ready | @liam | #32 | 20 h | | #7 db: schema migration convention | ready | @liam, @yuuhikaze | #32 | 20 h | | #14 web: sign-in flow and session | blocked | @felipe_bhrqz | #33 | 13 h | | #20 backend: real-time collaboration service | blocked | @yuuhikaze | #21 | 13 h | | #21 web: collaborative editing | blocked | @felipe_bhrqz | #34 | 13 h | | #22 backend: comments API | blocked | @yuuhikaze | #23 | 13 h | | #24 render: worker toolchains and output profiles | ready | @yuuhikaze | #25 | 20 h | | #27 backend: notifications and activity API | blocked | @yuuhikaze | #28 | 13 h | | #29 backend: reports API | blocked | @yuuhikaze | #30 | 1 h | | #31 db: demo dataset for the presentation | blocked | @liam | #32 | 13 h | | #32 deliverable: final SQL file and DER | blocked | @liam | #35 | 13 h | | #34 web: responsive, accessibility and regression pass | blocked | @felipe_bhrqz | #54 | 1 h | | #46 backend: admin API | blocked | @yuuhikaze | #47 | 1 h | | #48 web: admin area | blocked | @felipe_bhrqz | #54 | 1 h | | #54 qa: bug-fix round before the presentation | blocked | @yuuhikaze, @felipe_bhrqz, @liam | #36 | 1 h | | #55 devops: scripted demo recording tooling | blocked | @yuuhikaze | #36 | 1 h | <!-- watch:report -->
Collaborator

[BLOCKED] #2: @yuuhikaze this issue blocks #4 and has not been started (32 h).

— automation (scripts/watch.py)

[BLOCKED] #2: @yuuhikaze this issue blocks #4 and has not been started (32 h). — automation (scripts/watch.py)
Collaborator

[BLOCKED] #3: @yuuhikaze this issue blocks #45, #10, #4 and has not been started (32 h).

— automation (scripts/watch.py)

[BLOCKED] #3: @yuuhikaze this issue blocks #45, #10, #4 and has not been started (32 h). — automation (scripts/watch.py)
Collaborator

[BLOCKED] #5: @liam this issue blocks #32 and has not been started (32 h).

— automation (scripts/watch.py)

[BLOCKED] #5: @liam this issue blocks #32 and has not been started (32 h). — automation (scripts/watch.py)
Collaborator

[BLOCKED] #6: @liam this issue blocks #50, #31, #19 and has not been started (32 h).

— automation (scripts/watch.py)

[BLOCKED] #6: @liam this issue blocks #50, #31, #19 and has not been started (32 h). — automation (scripts/watch.py)
Collaborator

[BLOCKED] #7: @liam @yuuhikaze this issue blocks #32 and has not been started (32 h).

— automation (scripts/watch.py)

[BLOCKED] #7: @liam @yuuhikaze this issue blocks #32 and has not been started (32 h). — automation (scripts/watch.py)
Collaborator

[BLOCKED] #8: @felipe_bhrqz this issue blocks #48, #30, #16, #15, #14 and has not been started (32 h).

— automation (scripts/watch.py)

[BLOCKED] #8: @felipe_bhrqz this issue blocks #48, #30, #16, #15, #14 and has not been started (32 h). — automation (scripts/watch.py)
Collaborator

[BLOCKED] #9: @felipe_bhrqz this issue blocks #16, #15, #14 and has not been started (32 h).

— automation (scripts/watch.py)

[BLOCKED] #9: @felipe_bhrqz this issue blocks #16, #15, #14 and has not been started (32 h). — automation (scripts/watch.py)
Collaborator

[BLOCKED] #24: @yuuhikaze this issue blocks #25 and has not been started (32 h).

— automation (scripts/watch.py)

[BLOCKED] #24: @yuuhikaze this issue blocks #25 and has not been started (32 h). — automation (scripts/watch.py)
Sign in to join this conversation.
No description provided.