* docs: add beadcyte to community tools (Web UIs)
Local web app that draws bead history and a projected future: a
historical-median estimator, a greedy WIP-cap scheduler, and an
eight-signal triage score, each with its own uncertainty. Reads and
writes only through the bd CLI.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: correct beadcyte storage-access claim and normalize emphasis
The beadcyte entry said the tool "reads and writes exclusively through
the `bd` CLI ... never the Dolt files or `.beads/issues.jsonl`". The
first half is false for the shipped package. Measured against
beadcyte@0.9.0, the latest published version (tarball sha1
93964d9632cc1b1cc846f5d84f0dfa8a79a4ef57, matching the registry
shasum):
- The package starts exactly one process that is not `bd`:
`spawn("dolt", ["sql", "-r", "json", "-q", sql], ...)` with cwd
<project>/.beads/embeddeddolt (src/history-sql.mjs:250,
`doltSqlRunner`).
- `beadcyte freeze` reaches it through `readDoltDates`
(src/freeze-cli.mjs:110). `freeze` is a dispatched subcommand
(bin/beadcyte.mjs:37, 63-65). The path is on by default:
freeze-cli.mjs:33 sets `dolt: true`, and `--no-dolt` (:38) turns
it off.
- The author's own comment agrees: "`beadcyte freeze` is the ONE
place beadcyte reads Dolt directly ... read-only"
(src/history-sql.mjs:42-44).
Correcting an over-broad claim can easily introduce a new one, so each
clause of the replacement was checked:
- "reads and writes through the `bd` CLI": every other process the
package starts is `bd`. Writes go through `bd update`, including
freeze's own write-back (freeze-cli.mjs:127), and through
`bd dolt pull`/`push` (src/serve.mjs:498, 509).
- "read-only": `QUERIES` (history-sql.mjs:115-124) holds 4
statements, all SELECT. Every SQL call site passes one of them
(history-sql.mjs:302-303, 467-470).
- "never `.beads/issues.jsonl`": the package contains zero `jsonl`
references, so the entry still meets the page's compatibility bar
(docs/community-tools.md:8-11).
Emphasis: 51 of the page's 52 entries carry exactly one bold span, the
linked name. beadcyte carried three. Removing the bold from "happened"
and "expects to happen" brings it to 52/52.
Length: the correction adds 74 characters, bringing the entry to 1073.
That is still the longest of the 7 Web UIs entries, and 3rd on the
page after Beadazzle (1579) and Beads Dashboard (1300). Review
suggested trimming it to a feature summary. That suggestion is
optional and does not gate the review, and how the product is
described is the contributor's call, so this commit does not make it.
Gates: git diff --cached --check is clean. check-doc-flags.sh returns
rc=0 against the pinned v1.2.2 bd. check-doc-freshness.sh reports 68
PASS / 0 FAIL. go test ./test/docsync passes 8/8.
go test -tags integration -run TestDocFreshness ./scripts gives
37 pass / 0 fail / 1 skip.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Eddie the Engineer <adopt-pr@gascity.local>