knowledge: 8 insights — OKLCH dark-surface steps, benchmark-relative signals, multi-row reorder concurrency, Prisma CONCURRENTLY, graphify viz failure, newest-transcript measurement, fake-timer TTL isolation, fallback-source alert (+3 folds onto #179/#181, 1 already-merged drop)

[choiyounggi]

Knowledge flush — 12 insight(s) claimed: 8 ingested on this branch, 3 folded onto open PRs, 1 dropped as already merged

Run id 20260906-003715-45485 (headless auto-flush), branch knowledge/choiyounggi-20260906-003745, base origin/main at 6dcda6f (1.21.0). Claimed with queue-claim.js claim --max 12; 40 rows remain pending for later flushes.

Verified best-practice

#	Queue hash	Claim	Sources checked	How verified	Confidence
1	fbb4ea0373ad14b6	OKLCH lightness steps below L 30% collapse to ~1.1–1.3:1 contrast in sRGB; gate state cues on the measured ratio, carry identification on outline/chroma/shape	https://www.w3.org/TR/WCAG21/ (ratio formula), https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html (3:1 for UI components), https://www.w3.org/TR/css-color-4/ (OKLCH lightness is visual lightness; sRGB transfer function)	Recomputed WCAG ratios from the candidate's measured rgb bytes in Python: 13% vs 19% = 1.091, 13% vs 27% = 1.339 (exact match to the candidate). Re-derived OKLCH→sRGB with the CSS Color 4 matrices: all five rungs within ±2 bytes of the engine measurement. Agents confirmed all three URLs 200 with quotes	verified
2	2232cfdc9e06a8b7	Grade a per-entity signal on excess return over the benchmark for the same window; a population-wide burst is a shared driver	https://corporatefinanceinstitute.com/resources/equities/abnormal-return/ ("Excess Return = Actual Return − Expected Return", market index as expected), https://www.wallstreetprep.com/knowledge/information-ratio/ ("excess return over a benchmark")	Both URLs 200 with verbatim quotes; arithmetic in the field data checked (1,531,000→1,599,000 = +4.44%). Investopedia returned 402 and was excluded	verified
3	5a6ea1bb69d16261	Multi-row rewrite on a shared resource: parent-row lock in one transaction, deferrable unique position, explicit final-state rule, two-writer test	https://www.postgresql.org/docs/current/explicit-locking.html (FOR UPDATE), https://www.postgresql.org/docs/current/sql-createtable.html (DEFERRABLE), https://www.postgresql.org/docs/current/sql-set-constraints.html (DEFERRED checked at commit), https://www.postgresql.org/docs/current/sql-insert.html (ON CONFLICT DO UPDATE = UPSERT)	All four URLs 200 with quotes; field fix (pessimistic lock + single transaction + upsert) from the linkly-calendar review findings	verified
4	1c1a26a8abae7532	Check a DDL rule's premise (large live table) and the runner's ability to execute it (Prisma wraps multi-statement migrations in an implicit transaction, so CONCURRENTLY fails)	prisma/orm#22922 (title and body read via gh api; the reporter's reproduction: two-statement file fails, one-statement passes; a later comment shows a single statement split across lines also wrapped), prisma/orm#10601 (title "Disable transactions for a single migration", error 25001 quoted), prisma/orm#14456, https://github.com/prisma/prisma-engines/blob/main/schema-engine/ARCHITECTURE.md ("Why does Migrate not run migrations in a transaction by default?"), https://www.postgresql.org/docs/current/sql-createindex.html ("CREATE INDEX CONCURRENTLY cannot" run in a transaction block)	The candidate's prisma/prisma URLs redirect to prisma/orm; recorded the canonical URLs. Issue is still open (no fix), which the row reflects	verified
5	c20328d15c5d637f	graphify update on >5,000 nodes fails only at the HTML export; graph.json and the report are already written; no --no-viz on update	Installed source, graphifyy 0.4.23 (~/.local/pipx/venvs/graphifyy): watch.py _rebuild_code writes GRAPH_REPORT.md, to_json, then to_html; export.py MAX_NODES_FOR_VIZ = 5_000 raises ValueError("... Use --no-viz ..."); __main__.py update exits 1 on False; grep no-viz over the CLI finds only the error string. PyPI JSON API: latest is 0.9.54	Read the code paths directly; the row is version-scoped to 0.4.23 with a re-check instruction. The candidate's monkeypatch directive is kept as the "hook must exit 0" branch only	verified (0.4.23)
6	aae0d53b3d306e5e	Measure a live session's context from the newest transcript file, not the project directory	https://code.claude.com/docs/en/sessions (<project>/<session-id>.jsonl, project = cwd with non-alphanumerics replaced by -); dev-loop's own skills/orchestrate/scripts/token-report.sh header and SKILL.md lines 108–122 already encode the same rule	URL 200 with quote; field measurement (49 files, 10 spurious warn: lines, live session under threshold) from the candidate	verified
7	3bb4937f1288fef0	With fake timers, a "lock explicitly cleared" test whose wait ≥ TTL cannot fail; rewind the clock to before expiry and mutation-check the clear	https://vitest.dev/api/vi.html (vi.setSystemTime "simulates a user changing the system clock")	URL 200 with quote; field mutation check (commenting out lockouts.clear() reddened exactly the target test) from the candidate	verified
8	ef088fd050a74454	Alert on the primary source's success count reaching zero when a fallback silently takes over	https://sre.google/sre-book/monitoring-distributed-systems/ (symptoms vs causes; already the page's source). The agent found no primary text stating "fallback success must emit a signal" — the row is field-derived	7-day incident (pykrx dead, Naver fallback 29/30, 0 signals, runs logged green) from korea-data-suite / stock-signal-bot	field-tested (row); page stays verified for its existing content
9	00297bb2452bb72c	Worker done with a clean worktree, or "unexplained resets": the edits escaped to the main checkout; recover with git diff → git apply --3way	https://git-scm.com/docs/git-apply (--3way: "Attempt 3-way merge if the patch records the identity of blobs")	URL 200 with quote (agent + my own curl); field run i168 t2 (bats 21/21 after transplant)	verified
10	18392e61e52d0b0f	After merging worker branches into the integration worktree, re-sync installed deps and codegen before diagnosing "module not found" / undefined generated model as a regression	https://pnpm.io/cli/install (frozen lockfile "fails to install if the lockfile is out of sync"), https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/generating-prisma-client ("whenever you add models, change fields…"), https://git-scm.com/docs/git-worktree (already on the page)	URLs 200 with quotes; field run trip3 (7 suites Cannot find module 'undici', 2 e2e prisma.trip undefined, fixed by install + generate with no code change)	verified
11	13ce23861664767e	Before writing "reuse component X" in a design doc, grep the implementation and consumer count and record the command	No external source needed (the mechanism is the grep itself); field: LinklyModal.swift was a bottom sheet with one consumer, LinklyCalendarRangeLozenge had zero	Field evidence from the candidate; verifiable by re-running the recorded grep	field-tested
12	f1ba9bf617fbd101	graphify CLI exits 0 on missing node / missing file / JSON error; validate the artifact and branch on stdout	—	Already on main verbatim: code-graph-as-orientation-layer.md edge row "The CLI exits 0 on a missing node, a missing graph file, or a JSON decode error" plus the 0.4.23 source line, merged via #184 on 2026-09-04 from the same session	dropped — already merged

Nothing was upgraded to verified without a cited document or a reproduction I ran; #8 and #11 are labelled field-tested in the pages.

Existing-layer check

Pages read: infrastructure-agent-orchestration-code-graph-as-orientation-layer, infrastructure-agent-orchestration-worktree-isolated-workers, infrastructure-agent-orchestration-session-context-token-budget, infrastructure-observability-alerting, testing-quality-tests-that-cannot-fail, testing-quality-injected-clock-duration-assertions, testing-async-async-testing, frontend-design-anti-slop-visual-design, databases-schema-design-online-schema-changes, databases-transactions-optimistic-vs-pessimistic-locking, databases-transactions-isolation-level-selection, backend-common-integrations-estimate-derived-thresholds

Also read INDEX.md, the domain indexes for infrastructure, testing, frontend, databases, backend, qa and debugging, AGENTS.md, templates/page.md, and, on the open PR branches only (not on this checkout), semantic-conflicts-after-parallel-merge (#179) and checkable-claims-in-an-adopted-plan (#181).

Overlaps and outcomes:

• knowledge: streaming large result sets (server-side cursor blocked → fetchmany + write-only) #1 OKLCH — anti-slop-visual-design has the "+3% lightness per elevation level" rule; not a conflict (elevation is decorative), but a reader could over-apply it to state cues. Created a new page and appended a pointer to that row plus a related: link both ways.
• knowledge: kubelet resource metrics on embedded k8s; host-to-pod memory limit sizing #2 benchmark-relative — no existing page; estimate-derived-thresholds (same bot, integrations) and mape-aligned-point-prediction (ml) are the neighbours. New page; back-link added on estimate-derived-thresholds.
• knowledge: PID-1 tee log capture pattern, BSD/GNU date %3N feature detection #3 multi-row reorder — isolation-level-selection has the multi-row-invariant row (SERIALIZABLE or parent lock) and optimistic-vs-pessimistic-locking the version-column path, but neither covers the unique-position constraint or the final-state rule. New page; both existing pages gained a related: back-link.
• knowledge: kubelet resource-metrics, PID1 log flush, date %3N detection #4 Prisma CONCURRENTLY — online-schema-changes already says "Never inside a transaction block" for CONCURRENTLY; merged two edge rows (implicit runner transaction; premise absent on an empty table), five sources, applies_to widened to prisma.
• ingest(databases): online schema changes + autovacuum/wraparound #5 graphify viz failure — merged as one edge row into code-graph-as-orientation-layer next to the exit-0 row it extends.
• knowledge: kubelet resource metrics, cgroupns visibility, LLM completion validation, gateway alias defaults (4 insights) #6 newest transcript — merged as one edge row into session-context-token-budget. Body-only edit: PR knowledge: 9 insights — fresh-context review, gate parser/executor split, coordinator under tmux, sun_path limit, REPL sentinel await, allowlist bypass reproduction, version-drift gate, mock ts at emit (+3 folds onto #180/#181, 1 stale drop) #183 rewrites that page's related: line, so the frontmatter was left untouched to avoid a conflict; the source is recorded in the body's Sources list.
• knowledge: validating a check whose target does not exist yet (1 insight) #7 fake-timer TTL — injected-clock-duration-assertions is about float tolerance, not this; tests-that-cannot-fail is at 114 body lines and its related: line is rewritten by knowledge: 12 insights — deny rules under bypass, merged-tree gate, worker verify command, Kotlin daemon heap, extracted-method this (+7 merges) #179 and knowledge: 9 insights — fresh-context review, gate parser/executor split, coordinator under tmux, sun_path limit, REPL sentinel await, allowlist bypass reproduction, version-drift gate, mock ts at emit (+3 folds onto #180/#181, 1 stale drop) #183. Merged into async-testing (fake-timer mechanics page) as one edge row, body-only for the same reason (knowledge: 9 insights — fresh-context review, gate parser/executor split, coordinator under tmux, sun_path limit, REPL sentinel await, allowlist bypass reproduction, version-drift gate, mock ts at emit (+3 folds onto #180/#181, 1 stale drop) #183 rewrites its related:), with an inline link to tests-that-cannot-fail for the mutation proof.
• knowledge: spec/mapping artifact checks — coverage vs value validity, per-check negative controls, GFM pipe parsing (2 insights) #8 fallback alert — merged into alerting as one edge row + one Instead-of row, body-only (knowledge: 12 insights — dropzone copy vs drop handlers, destination-in mask chaining, media-query inset reset, spatial clamp, env restore vs pop, synthetic-corpus floor, plan-claim recompute, multi-name command -v, alert suppression key, sibling validators (+2 folds) #181 rewrites its related: line).
• knowledge: doc-conformance check controls + object-storage key persistence (5 insights to 2 pages) #9, knowledge: spec-document gates (4 axes + controls) and non-ASCII grep matching #10, knowledge: non-interactive CLI hangs, gates that read command text, editing a gated document (4 insights → 3 pages) #11 — folded onto open PRs (next section), no main-branch page touched.
• knowledge: non-interactive CLI stdin, LLM response completeness, externally-owned defaults #12 — duplicate of a merged row; nothing written.

No contradictions found. Lint: wiki-structure-checks.js wiki → 0 findings (281 pages); wiki-lint-prohibitions.js wiki → 0 violations; new pages 83/78/88 total lines (all bodies ≤ 120).

Open-PR check

Open knowledge/* heads listed with gh pr list --search "head:knowledge/": #183 (knowledge/choiyounggi-20260904-133717), #182 (…-20260903-214027), #181 (…-20260903-203836), #180 (…-20260903-184706), #179 (…-20260903-172728). Each was fetched and diffed against origin/main -- wiki/.

Candidate	Overlapping open head	Verdict	Action
#9 00297bb2452bb72c worker done / clean worktree / "resets"	#179 rewrites worktree-isolated-workers with the patch-transfer recovery rows (git diff → git apply --check → git checkout --)	fold	Added one edge-case row (the clean-worktree-at-done and "external resets" symptoms are the same incident; git apply --3way), extended the git-apply source bullet with --3way, added the i168 t2 field line. Pushed to #179 and commented
#10 18392e61e52d0b0f stale install/codegen after merge	#179 adds semantic-conflicts-after-parallel-merge (merged-tree result table)	fold	Added a row to the merged-tree result table, one Instead-of row, two doc sources (pnpm, Prisma generate) and the trip3 field line. Pushed to #179 and commented
#11 13ce23861664767e grep before writing "reuse X"	#181 adds checkable-claims-in-an-adopted-plan (adopter-side recomputation of a plan's claims)	fold	Added one edge-case row for the plan's author, the field line, and extended the page's load-when line in infrastructure/index.md on that branch. Pushed to #181 and commented
#6 newest transcript	#183 touches session-context-token-budget related: only	new (body-only edit here)	—
#7 fake-timer TTL	#183 touches async-testing related: only; #179/#183 touch tests-that-cannot-fail related: only	new (body-only edit here)	—
#8 fallback alert	#181 touches alerting related: only	new (body-only edit here)	—
#1, #2, #3, #4, #5	none of the five heads touch anti-slop-visual-design, online-schema-changes, code-graph-as-orientation-layer, the transactions pages, or the ml category	new	—
#12	not an open-PR overlap — already on main via #184	drop (pending-duplicate of merged content)	Retired

Expected merge friction: every open head appends to log.md, and #179/#180 touch INDEX.md (2 lines each); this branch appends nine log.md lines and edits the databases and backend rows of INDEX.md. frontend/index.md and infrastructure/index.md are touched by #181/#179/#183 in other rows. These are line-adjacent, not semantic, conflicts.

Routing decision

Candidate	Target	New page?	Why here
#1 OKLCH steps	frontend/design/lightness-steps-on-dark-surfaces.md	yes	frontend/design owns color/token decisions; trigger (dark ladder below L 30%, state cue) is new
#2 benchmark-relative	backend/common/ml/benchmark-relative-signal-classification.md	yes	No category for analytics exists; ml already holds the evaluation/calibration page (MAPE) and this is a grading-input rule of the same kind. Creating an analytics category for one page was rejected in favour of the closest fit; INDEX.md backend row now names it
#3 multi-row reorder	databases/transactions/multi-row-reorder-on-a-shared-resource.md	yes	Transaction boundary + constraint deferral + locking are DB-side mechanics; the app-side wrapper is linked (backend-common-orm-transaction-boundaries)
#4 Prisma CONCURRENTLY	databases/schema-design/online-schema-changes.md	merge (2 edge rows)	The page already owns CONCURRENTLY; the runner constraint and the empty-table premise are its edge cases
#5 graphify viz	infrastructure/agent-orchestration/code-graph-as-orientation-layer.md	merge (1 edge row)	Same tool, same page, adjacent to the exit-0 row
#6 newest transcript	infrastructure/agent-orchestration/session-context-token-budget.md	merge (1 edge row)	Measuring a session's context is that page's subject
#7 fake-timer TTL	testing/async/async-testing.md	merge (1 edge row)	Fake-timer mechanics live there; the cannot-fail proof is linked
#8 fallback alert	infrastructure/observability/alerting.md	merge (1 edge + 1 Instead-of row)	Alert design; sits beside the "absence of success" batch-job row
#9, #10	PR #179 pages	fold	see Open-PR check
#11	PR #181 page + its index line	fold	see Open-PR check
#12	—	drop	already merged (#184)

No new category was created. Indexes updated: frontend/index.md, backend/index.md, databases/index.md, INDEX.md (databases and backend route lines); log.md gained nine entries.

[github-actions]

Wiki agent gate: fail

test

• blocker [fact] a — b