Read and write each record through the store its config names #530
Reference in New Issue
Block a user
Delete Branch "item-354"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Item 354: the decisions, score anchors, comprehension history, reading cost and changelog are each read and written through
record_store, with a markdown file as the only backend so far.project-record open|save <record>gives agents the same path. A contract suite runs on the file store and on a fake.Review: security clean. Stability, product-owner and prose each took one round with no must-fix finding; their should-fix findings are fixed, except two:
plan_reasonsinbin/larv_review/plan.py, a place the seats found hard: the change only swaps three arguments there. Reading the three records together at the top would make a project that opts out of the comprehension check fail on a record it never reads, so the function keeps its shape; item 300 restructures it.ready_releaseinbin/deploy_release/cut.py: no test tells the changelog on the branch from the file in the clone, because with a tag in place the answer is the same for both.default_plan, which does the read, now has that test.The product-owner's nit that an empty copy is refused like a missing one stands: a missing copy reads as empty, and storing it would wipe the record.