chore: re-export issues.jsonl with memories, ignore generated dolt server config

bd export drops 'bd remember' memories unless --include-memories is passed,
and beads' own git hooks run the plain form, so a stray `git checkout` had
silently stripped all 15 memory records from the tracked export. Re-export
with the flag and record the trap in kb.pl.

.beads/dolt-server-config.yaml is machine-local generated state (absolute
cfg_dir, ephemeral port) alongside the already-ignored dolt-server.* files.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

.beads/.gitignore

@@ -49,6 +49,7 @@ dolt-server.log
 dolt-server.lock
 dolt-server.port
 dolt-server.activity
+dolt-server-config.yaml
 
 # Corrupt backup directories (created by bd doctor --fix recovery)
 *.corrupt.backup/

prolog-sessions/kb.pl

@@ -561,3 +561,9 @@ work_done('backlog-groom-2026-09-19',groom,'ran the five 2026-08-30 checks over
 decision('backlog-groom-2026-09-19',render_cache_name_collision,'improvise-cqi landed RenderCache as a flat grid-only wire type, while six open migration tickets (35e, n10, pca, 764, jb3, edp) were written against a fat per-widget cache of the same name. Two objects, one name, and nothing in the tree complains until someone writes from_app. Filed improvise-rkeq to decide the shape and made it block 35e rather than silently rewriting six tickets to match whichever shape a groomer preferred.').
 decision('backlog-groom-2026-09-19',retroactive_tickets_for_untracked_merges,'PR #7 (cloud-session tooling) landed 18 commits with no beads issue, the same gap the kb commits had. Filed improvise-3qz2 closed. Rule being followed: work that adds a durable capability -- a CI job, a hook, a script someone will later ask the provenance of -- gets a ticket even after the fact; a chore commit does not.').
 groom_check(dissolved_premise_test_gap,'a test-gap ticket rots differently from a code ticket: the gap can be closed by someone else work without anyone touching the ticket. Re-run each item against the test names before working it -- 2 of 7yx five items were already covered, by jc8 and by an import fix.').
+
+% ── Beads tracker maintenance (2026-09-19) ──────────────────────────────────
+decision('beads-maintenance-2026-09-19',export_drops_memories_by_default,'bd export omits the bd remember memories unless --include-memories (or --all) is passed, and .beads/issues.jsonl carries both. Regenerate it with: bd export --include-memories -o .beads/issues.jsonl. A plain bd export silently deletes all 14 memory records from the tracked file and the diff reads as an ordinary re-export. bd own auto-export refuses for the same reason, with an explicit shrink guard.').
+decision('beads-maintenance-2026-09-19',export_dependency_order_is_nondeterministic,'bd export emits each issue dependencies array in nondeterministic order, so a re-export of unchanged data still shows a ~23 line diff. Before committing, compare old against new with the dependencies arrays sorted; if nothing differs semantically, revert rather than commit the churn.').
+decision('beads-maintenance-2026-09-19',flake_beads_pin_verified,'flake.nix pins beads to github:gastownhall/beads/v1.3.0 (flake.lock rev f45b249ce6b40ba62aecc03949e6371e8f7c79d8). nix build of that ref yields beads-1.3.0, matching the local bd 1.3.0 that writes .beads/issues.jsonl, so the pinned tool and the tracked export agree on format.').
+decision('beads-maintenance-2026-09-19',prolog_save_session_is_destructive,'mcp saveSession to kb.pl rewrites the file from the in-memory clause database: it drops every comment and section header and reorders clauses, turning a 3-line append into a 708-line diff. Do NOT use saveSession on kb.pl -- append facts with a text edit and verify with: nix shell nixpkgs#trealla --command tpl prolog-sessions/kb.pl -g "kb_report, kb_consistent, halt".').