fix: use read-event with ctrl flag, add resize handling

- Switched back to read-event be :timeout 0.01 for proper key-event
  dispatch with the ctrl/alt/shift flags
- Fixed Ctrl+P/B/Q/L dispatch: check key-event-ctrl flag to
  construct :CTRL-<key> keyword symbol (read-event returns :P + ctrl=t,
  not :CTRL-P)
- Added :size-queried state flag and post-handshake backend-size re-query
- Removed hardcoded Connected v0.5.0 message from connect-daemon
- Removed Connected v0.7.2 system message (version shown in status bar)
- view-status now uses draw-rect for background (instead of dotimes loop)
- Added startup message showing backend type and detected dimensions

docs/.#DESIGN_DECISIONS.org

@@ -0,0 +1 @@
+user@amr.1407003:1778162380

docs/DESIGN_DECISIONS.org

@@ -948,8 +948,6 @@ For the philosophical foundations, see the Whitehead analysis in the Validation
 
 Alfred North Whitehead's two major bodies of work — /Principia Mathematica/ (1910–1913, with Bertrand Russell) and /Process and Reality/ (1929) — provide both the historical foundation and the descriptive vocabulary for Passepartout's architecture. The first gave us the type theory that structures the gate stack; the second gave us the process ontology that describes the pipeline.
 
-*** Historical Connection: PM → Lisp
-
 /Principia Mathematica/ is a direct ancestor of Lisp. Alonzo Church's lambda calculus (1930s), from which John McCarthy built Lisp (1958), was a response to PM's foundational program. PM's notation:
 
 #+BEGIN_EXAMPLE
@@ -961,8 +959,6 @@ Alfred North Whitehead's two major bodies of work — /Principia Mathematica/ (1
 
 These map directly to Lisp: ~(lambda (x) (φ x))~, ~(class (x) (φ x))~, ~(the (x) (φ x))~. McCarthy cited PM as an influence. The connection is genetic, not metaphorical.
 
-*** Process Philosophy as Architectural Vocabulary
-
 Whitehead's process philosophy is a metaphysics of /becoming/ rather than /being/. The fundamental entities are not substances but /processes/ (/actual entities/, /occasions of experience/). This maps precisely to Passepartout's pipeline architecture:
 
 | Whiteheadian Concept             | Passepartout Mapping                        | Significance                                     |
@@ -984,12 +980,8 @@ The foveal-peripheral model maps directly onto Whitehead's two modes of percepti
 
 Whitehead also gives Passepartout a /descriptive vocabulary/ that is precise, standard, and already maps perfectly to the design. "I am concrescing signal 47 through gates 0-8" is not poetry — it is a precise description of dispatcher operation. "Gate 3 has negatively prehended signal 136" means the secret-content gate rejected signal 136. "The satisfaction includes a file-write prehension with Merkle commit abc123" means the response contains a file write with the given Merkle hash. The agent uses this vocabulary in its ~/why~ output and in the ARCHITECTURE.org documentation.
 
-*** What Whitehead Does Not Contribute
-
 Not everything is useful. PM's full formalism — 300+ pages to prove ~1+1=2~ — is catastrophic as a reasoning engine. The /ideas/ (type theory, descriptions, propositional functions) are what matter, not the notation. Similarly, Whitehead's later concept of God (the "principle of concretion") and the full 25-category metaphysical system have no useful mapping to an agent architecture. Select the concepts that map; don't build a process-philosophy engine.
 
-*** Relation to the Neurosymbolic Architecture
-
 Passepartout is level 4 neuro-symbolic (symbolic gates + neural LLM, deterministic components coordinate heterogeneous systems). PM's type theory adds level-5 properties: /structural/ safety guarantees rather than /empirical/ ones. The dispatcher becomes not just a runtime gate stack but a type-theoretic framework where category errors are impossible by construction — just as PM made Russell's paradox impossible by construction. The Whiteheadian vocabulary reinforces the architectural identity: Passepartout is not a chatbot with safety checks. It is a /process/ — a continuous concrescence of prehensions producing satisfactions — whose safety is guaranteed by the type structure of the prehending entities.
 
 ** Historical Lineage — McCarthy's Advice Taker
@@ -1013,15 +1005,7 @@ The connection is not metaphorical. McCarthy cited /Principia Mathematica/ as an
 
 Reference: McCarthy, J. (1959). Programs with Common Sense. /Proceedings of the Teddington Conference on the Mechanization of Thought Processes./
 
-** Philosophical Validation — The Neurosymbolic Consensus
-:PROPERTIES:
-:ID:       design-validation
-:CREATED:  [2026-05-10 Sun]
-:END:
-
-Three papers from the neurosymbolic AI research community validate the architectural thesis from complementary angles.
-
-*** Marcus (2020): The Case Against Pure Deep Learning
+** Marcus (2020): The Case Against Pure Deep Learning
 
 Gary Marcus's "The Next Decade in AI" argues that deep learning alone is "data hungry, shallow, brittle, and limited in its ability to generalize." The paper demonstrates GPT-2 failing at basic commonsense reasoning:
 
@@ -1034,7 +1018,7 @@ Marcus's core claim — "we have no hope of achieving robust intelligence withou
 
 Reference: Marcus, G. (2020). The Next Decade in AI: Four Steps Towards Robust Artificial Intelligence. arXiv:2002.06177.
 
-*** Gaur & Sheth (2023): CREST — Trustworthy Neurosymbolic AI
+** Gaur & Sheth (2023): CREST — Trustworthy Neurosymbolic AI
 
 Gaur and Sheth present the CREST framework: Consistency, Reliability, user-level Explainability, and Safety build Trust — and they argue these require neurosymbolic methods. Their empirical finding: GPT-3.5 breached safety constraints 30% of the time when asked identical questions repeatedly. Claude's 16 safety rules and Sparrow's 23 rules provide no /inherent/ safety — they are heuristic guardrails that can be breached through prompt variation.
 
@@ -1042,7 +1026,7 @@ These findings validate three Passepartout design commitments: (1) prompt-level
 
 Reference: Gaur, M., & Sheth, A. (2023). Building Trustworthy NeuroSymbolic AI Systems: Consistency, Reliability, Explainability, and Safety. arXiv:2312.06798.
 
-*** Sheth et al. (2022): Knowledge-Infused Learning
+** Sheth et al. (2022): Knowledge-Infused Learning
 
 Sheth, Gunaratna, Bhatt, and Gaur define Knowledge-infused Learning (KiL) as "combining various types of explicit knowledge with data-driven deep learning techniques." They identify three infusion levels (shallow, semi-deep, deep) and position KiL as "a sweet spot in neuro-symbolic AI."