clean up and standardize types across the codebase, unify atomic operations, improve UTF-8 handling throughout the system, remove obsolete input and named queue interfaces, redesign process preparation and creation, tighten IPC and service boundaries, improve error handling and reliability, minor documentation cleanup, fix doom surfaces, fix panic in ini parsing.

docs.md

@@ -37,7 +37,7 @@ nt-lite is a clean-design hobby kernel. It is not a stable compatibility platfor
 
 ## Breaking changes
 
-Breaking changes are allowed. When making one:
+Breaking changes are encouraged. When making one:
 
 1. Define the new model.
 2. Move every user to it.
@@ -50,12 +50,10 @@ Breaking changes are allowed. When making one:
 - Generate patches from the repository root.
 - Paths must be rooted as `code/...`.
 - `git apply <patch>` should work from the repository root.
-- Do not require `--directory=code`.
 - Keep generated artifacts out of the source tree unless requested.
 - When asked to provide the full tree, also provide the patch.
 - The patch is for review; the full tree is for reproducing the exact baseline.
 - Avoid optimistic claims.
-- Say exactly whether a change was apply-checked, syntax-checked, built, booted, or runtime-tested.
 - Do not introduce compatibility aliases unless they are intentionally supported API.
 
 ## Comment style