\n\t\t\t\t\t{\n\t\t\t\t\t\t/*\n\t\t\t\t\t\t * The page itself, behind its contents rather than around them.\n\t\t\t\t\t\t *\n\t\t\t\t\t\t * It runs past the bottom of the window, so the ring, the shadow and\n\t\t\t\t\t\t * the two square corners that would say where it ends are all below\n\t\t\t\t\t\t * the fold — the page reads as continuing rather than as stopping\n\t\t\t\t\t\t * short. Its contents cannot go with it or the last line of the plan\n\t\t\t\t\t\t * would be off screen, which is why this is a sibling and not a\n\t\t\t\t\t\t * wrapper. The inset either side is the same four pixels `main` pads\n\t\t\t\t\t\t * by, measured from the padding box the two of them share.\n\t\t\t\t\t\t */\n\t\t\t\t\t}\n\t\t\t\t\t\n\n\t\t\t\t\t{\n\t\t\t\t\t\t/*\n\t\t\t\t\t\t * Both handles, ahead of the plan and not after it.\n\t\t\t\t\t\t *\n\t\t\t\t\t\t * They are positioned, so where they sit in the markup decides\n\t\t\t\t\t\t * nothing about where they are drawn — it decides only what order\n\t\t\t\t\t\t * they are tabbed to, and that is the whole reason they are here.\n\t\t\t\t\t\t * The plan is a Lexical surface, and `listsPlugin` mounts\n\t\t\t\t\t\t * `TabIndentationPlugin`, which calls `preventDefault` on Tab\n\t\t\t\t\t\t * before it has looked at `shiftKey`: Tab indents and Shift-Tab\n\t\t\t\t\t\t * outdents, so focus that reaches the editor does not leave it in\n\t\t\t\t\t\t * either direction. Anything behind it in the tab order is\n\t\t\t\t\t\t * unreachable. Handles that draw nothing at rest have only the tab\n\t\t\t\t\t\t * order to be found by, so behind the editor is nowhere at all.\n\t\t\t\t\t\t *\n\t\t\t\t\t\t * Left before right, so the order runs along the screen.\n\t\t\t\t\t\t */\n\t\t\t\t\t}\n\t\t\t\t\t{chat && (\n\t\t\t\t\t\t\n\t\t\t\t\t)}\n\t\t\t\t\t{decisions && (\n\t\t\t\t\t\t\n\t\t\t\t\t)}\n\n\t\t\t\t\t

{plan}

\n\t\t\t\t