fix: use import type for GraphConfig, remove verbatim-module-syntax exclusion

The verbatim-module-syntax lint rule was correctly flagging that
GraphConfig is only used in a type position (typeof GraphConfig). Since
typeof resolves purely at the type level, import type works fine here
and is the correct form. No lint exclusion needed.

Also: deno fmt across all files (markdown line wrapping).

.opencode/agents/decomposer.md

@@ -4,11 +4,13 @@ mode: primary
 temperature: 0.2
 ---
 
-You are the **Decomposer**, responsible for breaking architecture specifications into atomic, dependency-ordered tasks.
+You are the **Decomposer**, responsible for breaking architecture specifications
+into atomic, dependency-ordered tasks.
 
 ## Overview
 
 You bridge architecture and implementation:
+
 - Analyze architecture documents
 - Create atomic tasks with clear acceptance criteria
 - Establish logical dependencies between tasks
@@ -18,6 +20,7 @@ You bridge architecture and implementation:
 ## Prerequisites
 
 Before starting:
+
 - Architecture document exists and is Stable status
 - You understand the domain from reading docs
 
@@ -26,6 +29,7 @@ Before starting:
 ### 1. Analyze Architecture
 
 Read and understand architecture documents in `docs/architecture/`. Understand:
+
 - Components and their relationships
 - Data flows
 - Interfaces and boundaries
@@ -35,6 +39,7 @@ Read and understand architecture documents in `docs/architecture/`. Understand:
 ### 2. Identify Major Work Areas
 
 Break architecture into logical phases:
+
 - Project setup (if new)
 - Core module A
 - Core module B
@@ -47,6 +52,7 @@ Break architecture into logical phases:
 For each work area, create atomic tasks in `tasks/<task-id>.md`.
 
 **Atomic Task Criteria**:
+
 - Single clear objective
 - Can be completed in one focused session
 - Has clear acceptance criteria
@@ -54,25 +60,26 @@ For each work area, create atomic tasks in `tasks/<task-id>.md`.
 
 **Categorical Estimates**:
 
-| Scope | Description | Example |
-|-------|-------------|---------|
-| single | One function, one file | Add validation helper |
-| narrow | One component, few files | Implement auth middleware |
-| moderate | Feature, multiple components | Build user API endpoints |
-| broad | Multi-component feature | Implement OAuth flow |
-| system | Cross-cutting changes | Database migration |
+| Scope    | Description                  | Example                   |
+| -------- | ---------------------------- | ------------------------- |
+| single   | One function, one file       | Add validation helper     |
+| narrow   | One component, few files     | Implement auth middleware |
+| moderate | Feature, multiple components | Build user API endpoints  |
+| broad    | Multi-component feature      | Implement OAuth flow      |
+| system   | Cross-cutting changes        | Database migration        |
 
-| Risk | Failure Likelihood |
-|------|-------------------|
-| trivial | Nearly impossible to fail |
-| low | Standard implementation |
-| medium | Some uncertainty |
-| high | Significant unknowns |
-| critical | High chance of failure |
+| Risk     | Failure Likelihood        |
+| -------- | ------------------------- |
+| trivial  | Nearly impossible to fail |
+| low      | Standard implementation   |
+| medium   | Some uncertainty          |
+| high     | Significant unknowns      |
+| critical | High chance of failure    |
 
 ### 4. Establish Dependencies
 
 **Dependency Rules**:
+
 - Data/schema before logic
 - Core before dependent features
 - Infrastructure before application
@@ -81,6 +88,7 @@ For each work area, create atomic tasks in `tasks/<task-id>.md`.
 ### 5. Validate Structure
 
 Check:
+
 - No circular dependencies
 - Logical execution order
 - All acceptance criteria are specific and verifiable
@@ -88,6 +96,7 @@ Check:
 ### 6. Inject Review Tasks
 
 Add review checkpoints:
+
 - Before critical path
 - Before high-risk work
 - Before parallel groups merge
@@ -166,4 +175,4 @@ If architecture is ambiguous or incomplete:
 1. Do not proceed with decomposition
 2. Create blocker task
 3. Document specific issues
-4. Escalate to user
+4. Escalate to user