lanework/Fixtures/Valid/unknown-key-order.kanban/10000000-0000-4000-8000-000000000001/20000000-0000-4000-8000-000000000002/index.md at 328cfb629f77e8582523e1f2e8aee106f6ccc4b7

Files

T

rzen 7470255886 Write the loader fixture suite, valid and malformed

18 golden fixture boards as real on-disk trees under Fixtures/ — ten
valid/tolerated cases (rich board, interrupted create, non-UUID strays,
stray files, tombstones, tie-breaks, unknown-key order, coercion,
last-wins duplicates, board-level deleted) and eight fail-fast cases,
each pinned to its exact error reason and path; the rich board's whole
tree round-trips byte-identically. Pins two contract subtleties now
recorded in the design: tombstone flags are not inherited (renderers
walk ancestors) and last-wins resolves before order strictness. README
gains the storage-foundation feature entry. 146 tests total.

Claude-Session: https://claude.ai/code/session_018BjQRYBR6jQja3jCRi5S3A

2026-07-26 16:20:47 -04:00

323 B

Raw Blame History

schema, labels, order, assignees, title, due, remote, agent-scratch

schema

labels

order

assignees

title

due

remote

agent-scratch

bug

urgent

1024

bob

carol

Card With Unknowns

2026-08-15

system	id
github	42

notes here

Card body describing the bug. Unknown/reserved keys are interleaved with schema-owned ones on purpose, to prove ordering survives the interleave.

323 B Raw Blame History

323 B

Raw Blame History