docs: unwrap hard-wrapped Markdown to one line per paragraph

Hard line breaks mid-paragraph make docs harder to edit and diff — a
one-word change reflows and re-diffs the whole paragraph. Reflow all
tracked non-vendor Markdown (plus vendor/AGENTS.md) so each prose
paragraph is a single line; soft-wrapping is the editor's job. Fenced
code, tables, and list structure are preserved (wrapped list items fold
to one line per bullet). Documents the convention in AGENTS.md.

packages/README.md

@@ -1,10 +1,6 @@
 # Packages
 
-Harness packages, all under the `@deepseek-ai/dsh-*` scope. Each package is a
-Cordis service (microkernel plugin-style): it exports a default `Service` class
-that gets registered via `ctx.plugin()`, declares its ctx key and events through
-declaration merging, and exposes extension points through `ctx.effect()`,
-`ctx.on()`, and `ctx.waterfall()`.
+Harness packages, all under the `@deepseek-ai/dsh-*` scope. Each package is a Cordis service (microkernel plugin-style): it exports a default `Service` class that gets registered via `ctx.plugin()`, declares its ctx key and events through declaration merging, and exposes extension points through `ctx.effect()`, `ctx.on()`, and `ctx.waterfall()`.
 
 ## Dependency graph
 
@@ -17,9 +13,7 @@ dsh-tools         ← dsh-llm, dsh-system-prompt, dsh-agent
 dsh-agent-loop    ← dsh-llm, dsh-session, dsh-system-prompt, dsh-tools, dsh-agent
 ```
 
-The rule: plugins depend on interfaces, never on the concrete loop.
-`dsh-agent-loop` is swappable — UI/hook/tool plugins keep working against the
-`dsh-agent` vocabulary if the loop is replaced.
+The rule: plugins depend on interfaces, never on the concrete loop. `dsh-agent-loop` is swappable — UI/hook/tool plugins keep working against the `dsh-agent` vocabulary if the loop is replaced.
 
 ## What goes where
 
@@ -32,25 +26,13 @@ The rule: plugins depend on interfaces, never on the concrete loop.
 | `agent/` | Agent interface, registry, `agent/*` event vocabulary | `ctx.agents` |
 | `agent-loop/` | THE concrete plugin: `LoopAgent` + the loop driver | `ctx.agentLoop` |
 
-Each package has its own `README.md` with purpose, service API, events,
-extension points, and deliberate non-goals (TODOs).
+Each package has its own `README.md` with purpose, service API, events, extension points, and deliberate non-goals (TODOs).
 
 ## Conventions (applied across all harness packages)
 
-- **Registrations are effects**: every contribution (adapter, tool, section,
-  agent, event listener) goes through `ctx.effect()` / `ctx.on()`, so disposal
-  and HMR clean up automatically. Every `register()` returns the disposer.
-- **Declaration merging for events and ctx**: services declare their events in
-  `declare module 'cordis' { interface Events { ... } }` and their ctx key in
-  `interface Context`.
-- **Waterfall semantics**: `ctx.waterfall` listeners receive `(...args, next)`
-  and MUST call `next()` to delegate; returning without it short-circuits (the
-  veto mechanism).
-- **Extensible unions**: `ContentBlockMap`, `MessageSourceMap`,
-  `FinishReasonMap`, `TurnTriggerMap`, `TurnEndReasonMap`, and `SessionEventMap`
-  use the merge-extensible-map pattern so plugins can add variants via
-  declaration merging.
-- **ESM everywhere**; imports use package names across package boundaries,
-  `.ts` extensions within a package.
-- **Tests**: vitest, colocated under `packages/<name>/tests/*.spec.ts`. Every
-  registry needs an HMR-safety test. Err on the side of more tests.
+- **Registrations are effects**: every contribution (adapter, tool, section, agent, event listener) goes through `ctx.effect()` / `ctx.on()`, so disposal and HMR clean up automatically. Every `register()` returns the disposer.
+- **Declaration merging for events and ctx**: services declare their events in `declare module 'cordis' { interface Events { ... } }` and their ctx key in `interface Context`.
+- **Waterfall semantics**: `ctx.waterfall` listeners receive `(...args, next)` and MUST call `next()` to delegate; returning without it short-circuits (the veto mechanism).
+- **Extensible unions**: `ContentBlockMap`, `MessageSourceMap`, `FinishReasonMap`, `TurnTriggerMap`, `TurnEndReasonMap`, and `SessionEventMap` use the merge-extensible-map pattern so plugins can add variants via declaration merging.
+- **ESM everywhere**; imports use package names across package boundaries, `.ts` extensions within a package.
+- **Tests**: vitest, colocated under `packages/<name>/tests/*.spec.ts`. Every registry needs an HMR-safety test. Err on the side of more tests.