Realign code with the 2026-07-31 findings-resolution rulings

The full bullet list from Implementation card bf080d9a — both ruling
batches, including the three appended mid-session by 16ef377:

- Restore subjects compose the inverse, never nest: crossing "Undo: S"
  emits "Redo: S" and vice versa; parity, not stack depth, reads a
  legacy double prefix (GitHistoryProvider.restoreSubject).
- Git-operation failures join the one-shot failure banner tier:
  BannerCenter.GitFailureBanner (undo/redo/branchSwitch/addGit), error
  tone at failure rank merged with write one-shots by recency; the
  postLoss compromise is retired at both AppModel wirings.
- order/schema optional below the board root: append-at-end reading
  (ordered siblings first, folder-name tie-break among the order-less),
  schema reads 1, both coerce-tier logged; the root keeps its
  requirements. Ranks.resolvedOrders materializes finite ranks so
  models and placement math stay untouched; first Writer rewrite
  stamps a real rank on touch, placement against an order-less sibling
  stamps that sibling inline in the same bracket. Agent guide v10
  teaches optional keys and zero-read filing. Hostile-YAML order
  shapes become coercion tests; Fixtures/Valid/optional-keys.kanban
  replaces the four retired Malformed boards.
- .gitignore is the relocation-heal noise gate: GitignoreRules pure
  matcher (standard semantics, board-root file only), loader consults
  it once per walk so matched loose files keep the stray posture;
  seeded (.DS_Store + .*.lanework-*) at board creation and template
  instantiation, healed in when missing at open — repo-nested
  included; empty file honored, existing files never edited; the
  committer's obedience via libgit2 status is pinned by test.
- Comments crash-residue sweep gates on step ownership: HistoryStep
  derives backing from its own undo expectations, backedContent unions
  both stacks, the sweep purges per-entry only what no live step owns.
- Skip-purge decoupled (16ef377): a stale-skipped coarse step strands
  whole in NativeHistoryProvider.strandedSteps — still backing, retired
  only at session end; clean exits purge as before.
- Coarse close step named "Changes to '<card>'"; the fine body-edit
  wording never leaks onto the board menu.
- Branch-switch settle clears every open card window's fine stack on
  Save All and Discard alike; the empty fold registers no coarse step.
- Close flush awaits its covering snapshot (quiesce + one generation
  bump, 1s bound), and an explicit flush now queues behind an
  in-flight one instead of skipping — the audit-caught interleaving
  could lose a close flush permanently when the debounce fired inside
  the close sequence; regression tests force both races.
- Commit comment bullets sort chronologically by created, not UUID.
- The production-unwired CardBodyEditSession.editSessionDidChange seam
  is deleted with its seam-only tests.
- Composition-root pins: beginSession composes the committer with the
  store's own EchoLedger and binds the announcer (the miswire class).
- Deliberate 06 conformance pass over every 2026-07-31-tagged
  sentence: fixed Change-custom-key subjects (the retired named
  generic was the only producer), the unbuilt Replace attachment
  vocabulary, heal commits now authored Lanework Integrity, the config
  reader scopes identity to plain [user] sections, add-git re-runs
  detection at create (a stale mode-none could initialize inside the
  user's repo), and add-git failures answer at the form or the banner.
  Structural residue filed on the Redesign board.

2554 tests / 439 suites green.

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

Kanban/Git/CommitMessageComposer.swift

@@ -75,6 +75,23 @@ public struct CommitMessageRequest: Sendable {
     /// be read, or has been deleted.
     public let agentGuideText: String?
 
+    /// **When each of this commit's comments was created** — keyed by the comment folder's
+    /// board-root-relative path, as `CommitMessageEngine.commentFolder(of:)` spells it.
+    ///
+    /// The second value on this struct that a *file* has to be read for, and it is here for
+    /// `agentGuideText`'s reason exactly: "a commit's comment bullets sort chronologically — by the
+    /// comments' own `created`, folder name on ties" (06 ▸ Rules ▸ Auto-commit, blessed 2026-07-31),
+    /// and `created` lives in a comment's own `index.md` because comments are window-scoped and the
+    /// board snapshot never carries them (01-storage-format.md § Enhanced schema). The flush resolves
+    /// it once (`GitAutoCommitter.commentTimestamps(for:boardRoot:)`) and the engine stays a pure
+    /// function of values.
+    ///
+    /// **Missing is normal, not a defect.** A comment whose folder left the tree in this very commit
+    /// (the close purge), one whose `index.md` does not parse, one written by hand with no `created`
+    /// at all — each is simply absent here and sorts after its dated siblings in folder-name order,
+    /// which is `CommentThread.sorted`'s own fallback for the same field.
+    public let commentTimestamps: [String: Date]
+
     public init(
         boardRoot: URL,
         changedPaths: [GitChangedPath],
@@ -82,7 +99,8 @@ public struct CommitMessageRequest: Sendable {
         isRootCommit: Bool,
         snapshot: BoardModel?,
         previousSnapshot: BoardModel? = nil,
-        agentGuideText: String? = nil
+        agentGuideText: String? = nil,
+        commentTimestamps: [String: Date] = [:]
     ) {
         self.boardRoot = boardRoot
         self.changedPaths = changedPaths
@@ -91,6 +109,7 @@ public struct CommitMessageRequest: Sendable {
         self.snapshot = snapshot
         self.previousSnapshot = previousSnapshot
         self.agentGuideText = agentGuideText
+        self.commentTimestamps = commentTimestamps
     }
 }