Melvin StroblandClaude Fable 5
8c82549cf6
The browser half of M3. Flows open on a full-bleed canvas with their chrome floating over it: flow tabs top, dock bottom, node settings in a panel on the right that leaves the graph visible and running behind it. - Connections are derived, not stored. A node declares the messages it reads and publishes; every matching pair draws an edge, so two producers of one message converge on their consumer. Dragging output to input is shorthand for pointing that input at the producer's message, and asks before it replaces an existing one. - Values land on the edges as they flow, over a websocket that feeds a store outside React, so a value arriving re-renders its own chip and nothing else. Clicking an edge shows the last payload and when it arrived. - Node source is edited in Monaco, loaded only when a panel opens and themed from the design tokens. - Edits autosave; identical documents are skipped server-side, so a quiet canvas writes nothing. - Validation from the API shows on the node it belongs to and is summarised in the dock, where each entry pans to its node. - Works on a phone: touch-connect, 44px dock targets, and the node panel becomes a full-screen sheet. Two new tokens (--status-success, --font-mono) are mirrored in the website repo and recorded in DESIGN-GUIDELINES.md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016WzrvW7rjQbynnhF6pxh6i
3.8 KiB
3.8 KiB
This file captures tasks which derive from roadmap tasks (unfinished, deferred), bugs encountered during usage and feature requests/improvements which are not fitting directly in the roadmap. Always sort by priority and put tasks blocked by other tasks/features at the dedicated section. When working on a task, check for other, similar tasks that could be resolved on the way. Use following pattern to classify tasks: TYPE/SCOPE Where TYPE could be BUG, FEAT, PERF, CHORE and SCOPE could be UX, UI, FLOW, NODE, API, INFRA, DOCS appended by MOBILE if only for mobile use case. Don't write temporary reasons for deferring a task in the task description (only strategical reasons should be noted). Deferring because out of scope is fine, but don't mention deferring than.
Open
- BUG/UI: six template Playwright specs fail on validation copy that no longer matches
(
login,sign-up,reset-password,user-settingstheme persistence). Unrelated to the flow editor, which passes; fix or delete them with theItemcleanup. - CHORE/UI:
bunx playwright teststarts a dev server on :5173, which is not in the API'sBACKEND_CORS_ORIGINS, so every spec fails at login. Run against the integrated stack withPLAYWRIGHT_BASE_URL=http://app.localhost, or add the dev origin to CORS. - FEAT/UI: no undo on the canvas. Deleting a node autosaves immediately, so a mis-click costs the node's source.
- PERF/UI: the Monaco chunk is 2.6 MB. It only loads when a node panel opens, but the editor could be trimmed further or swapped for CodeMirror if that becomes a problem.
- FEAT/UI: renaming a message updates only the node being edited; the nodes consuming it keep the old name and quietly disconnect. Offer to rename across the flow.
- CHORE/INFRA: port the n3xd CI workflows (pre-commit, backend tests, Playwright shards,
compose smoke) to
.gitea/workflows/. The Gitea instance runs Gitea Actions and needs CI enabled per repository. - CHORE/FLOW:
app/flow/nodes.pyandstate.pyare excluded from strict mypy ([[tool.mypy.overrides]]inpyproject.toml). The node classes still carry prototype typing and redis-py types its calls as sync/async unions. Shrink the exclusion as each integration is revisited. - FEAT/API: per-hook shared secrets for
HttpNodewebhooks. They are mounted unauthenticated under/hooks/{flow}/…because devices cannot present a JWT. - FEAT/FLOW: state does not survive a restart — the engine runs on
MemoryStateunlessREDIS_HOSTis set, and there is no Redis compose service yet. - CHORE/FLOW: rotating
SECRET_KEYmakes the stored secrets unreadable, since the Fernet key is derived from it. Needs a re-encrypt path before anyone rotates in production. - PERF/FLOW: every save rebuilds the whole pipeline. Fine at the current flow count; rebuild only the touched flow when it starts to show.
- FEAT/UI: reintroduce
--chart-*tokens as one designed sequential scale when the first chart lands. The stock shadcn five were dropped because their light and dark values are unrelated hues. - CHORE/API:
backend/app/models.pystill holds the template'sItemmodel. It has no purpose now that flows are persisted and can go with its routes and tests. - PERF/UI: both frontend bundles exceed the 500 kB warning threshold. Revisit chunking once the canvas and editor are in, since they will dominate.
Blocked
- FEAT/INFRA: MQTT broker and InfluxDB compose services for local development. The node types exist; a local broker would make them testable without external hardware.
- CHORE/INFRA:
bun installinside the frontend Docker build intermittently fails with "Fail extracting tarball" for several packages at once, and succeeds on a plain rebuild. It looks like concurrent extraction under memory pressure. Pin down or retry in the Dockerfile if it starts costing CI time.