picatz / picatz/flowstate

Index: the 2026-09-06 review pass — 62 issues across correctness, security boundaries, drivers, CI and velocity, agents, enterprise operations, and community, grouped for triage

Open
#1,776 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/umbrella
Dominant language
Go
Stars
9
Forks
0
Avg merge
3h 3m
Merged PRs (30d)
509

Description

This is an index, not a plan. Every issue below was filed against eb8172f during one review pass that read the tree, ran the CLI, the local driver, flow server dev, and flow server --webhook, and measured what it claims. Each issue names its evidence; where a claim was inferred rather than observed the issue says so. Nothing here is ordered by priority; the first two groups are the ones a maintainer would want to read first because they are defects reproduced against a running system.

Defects reproduced against the durable driver or a boundary

  • #1769 an authored expression under the CEL cost limit spins a workflow task forever (deadlock panics), while the local driver completes it
  • #1757 validate and run local accept 4,000 steps and a 10,000-character id that the server refuses; schema rules never run locally
  • #1768 netpolicy decides only in the socket hook: literal targets burn the timeout as "undecided", a denial can be masked
  • #1775 the canonical Stripe example keys idempotency on the signature header; provider retries start duplicate runs
  • #1770 a 40-level signal or webhook payload is accepted while a 33-level input is refused
  • #1774 webhook deliveries and refusals leave no audit record
  • #1772 the list page token is unsigned; a forged cursor is accepted
  • #1751 Run has no request idempotency key; a retried submit double-starts
  • #1773 every: 1s schedules are accepted with no floor or per-tenant count
  • #1765 literal depth is bounded at 32 for input defaults and 64 for vars: and step values
  • #1764 NaN/Infinity floats leak the tagged encoding into the run document
  • #1766 CEL parser limits are reported as a bare number
  • #1767 --input-file is the one unbounded file read
  • #1759 three CLI transcripts (flow test refusal without a reason, fmt --check wording, range did-you-mean)
  • #1758 local driver cost per top-level step is quadratic
  • #1761 no panic recovery on the server's Connect chain

Internals: redundancy, patterns, tests, debt

#1714 truncate helpers · #1715 options-style decision · #1716 stdlib log sites · #1717 ad-hoc caches · #1718 test reach · #1719 compat ledger · #1720 activity input pruning · #1721 fuzzers per boundary parser · #1722 global test seams · #1723 bare context.Background() on the workflow side · #1724 untagged dependencies · #1725 Value-tree walkers · #1763 complexity ratchet · #1762 worker memory tuning · #1749 threat-model Verified by: ledger · #1760 citation checker

CI, velocity, agents, review

#1726 CI critical path · #1727 test failures as annotations and JSON · #1728 commit and PR conventions as a check · #1729 tool directive · #1731 agent hook binary with compile feedback · #1738 attach to a running dev server · #1739 coverage in the deep tier · #1750 Scorecard, CodeQL, dependency review · #1742 llms.txt

Enterprise operations and security program

#1730 per-tenant admission control · #1732 container image and Kubernetes base · #1733 per-action authorization and scopes · #1734 KMS and Vault Transit signer · #1735 cloud secret providers · #1736 upgrade, rollback, backup runbook · #1737 alert rules · #1745 real-process chaos tier · #1746 load and throughput evidence · #1747 claim-check payload codec · #1748 the gate page decision · #1752 quorum gates · #1753 bulk operations · #1754 rerun from a failed step · #1755 usage metering · #1756 per-namespace keys and erasure · #1771 flow run --detach

Community and positioning

#1740 the flow binary name collision · #1741 docs site · #1743 community health files · #1744 positioning against alternatives

Probes that came back clean, for the record

YAML aliases, duplicate keys, bidi and zero-width characters, integer overflow, deep parentheses, call: path traversal (absolute, climbing, self-cycle), dotted-decimal SSRF spellings and the metadata address, 50 concurrent submits, file:// and gopher:// URLs, oversized Flowfiles, malformed signatures and stale timestamps on webhooks, a 2 MiB webhook body. Each refused correctly and quickly.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This issue is an index rather than an implementation plan and points to issues #1769 through #1776 and many other investigations. Start by reading the linked issue that matches the area you want to work on, along with its cited evidence. Done means completing a separately scoped issue; this index alone does not define a change or acceptance test.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, ci-cd, cli, documentation, security
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.