Tech-debt remediation: lib/bin split + D1–D5 resolved (#37)

* fix(gossamer): Week 1 tech-debt — wire dead registry/settings/resources cmds, drop speculative scaffolding

D1: service registry is a fixed env-driven set; wire service_list
(get_registry) + service_set_url (update_service_url); remove vestigial
register/unregister command stubs (no backing fns).
D2: wire settings_save + llm_coding_system_resources (read_system_memory
+ SystemResources + new CPU sampler); remove unused WorkspaceLock,
PendingAction, SpawnRequest.task_list. clippy -D warnings clean.
D5: rewrite TECHNICAL_DEBT.md as verified 30-day plan; fix arch link.
Also de-Tauri'd llm_coding/commands.rs header (Gossamer).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* feat(coprocessor): Week 2 — real Zig FFI dynamic loading (D4)

Add libloading 0.8 dep (once_cell already present). FfiState now owns
the loaded libloading::Library; copro_load_ffi does a real dlopen +
copro_init; copro_ffi_dispatch resolves copro_dispatch/copro_free from
the live handle and calls the C ABI (was a stub). Symbols resolved
per-call (no self-referential 'static storage). De-Tauri'd coprocessor
comments. Removed stale libloading/once_cell TODOs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* refactor: lib/bin split — testable logic crate; wire orphaned coprocessor (D3)

Add [lib] panll target (GTK-free): http_client, service_registry,
settings, identity, groove, llm_coding + the previously-orphaned
coprocessor (declared by no crate root → never compiled; D4's FFI fix
now actually builds and is tested). main.rs keeps only system_tray
(gossamer_rs/GTK) and imports the rest via use panll::*.

cargo test --lib now runs WITHOUT linking libgossamer/GTK: 18/18 pass
(6 new D3 tests for http_client + service_registry, 12 coprocessor).
Cleared 11 latent clippy lints surfaced once coprocessor compiled
(10 empty-line-after-doc, 1 should_implement_trait — justified allow).
clippy --all-targets -D warnings clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore: Week 4 — hardening, hypatia reconcile, changelog, doc finalize (W4)

- Fold cross-module integration tests into the lib test surface so they
  run via cargo test --lib (no GTK bin build): 23/23 pass.
- Reconcile .github/hypatia-rules/panll-v0.2.0-fixes.yml v1->v2: retire 8
  stale panic-attack rules that false-positive on now-correct code; keep
  one precise regression guard (panll-cmd-disabled); fix doc-ref path.
- CHANGELOG.md: document lib/bin split, coprocessor wiring, add/remove/fix.
- TECHNICAL_DEBT.md: mark D1-D5 resolved with execution log; record
  honest environment caveat (bin link needs GTK) and follow-up debt
  F1 (40 orphaned dirs) / F2 (coprocessor IPC wiring) / F3 (dev env).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: correct F1 — 38 orphaned dirs are unwired panel backends, not dead code

Inspection showed every 'orphan' dir is a real PanLL panel backend
(aerie/hypatia/ai/farm/provenance/…), orphaned by the same defect as
coprocessor. Decision: integrate, not delete. Added F1 integration
workstream plan (coprocessor pilot → census → bulk wire).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

.github/hypatia-rules/panll-v0.2.0-fixes.yml

@@ -1,230 +1,77 @@
-# Hypatia Scanner Rules for PanLL v0.2.0 Fixes
-# 
-# These rules detect and remediate common issues found during the v0.2.0 panic attack
-# Rules are designed to work with the gitbot fleet for automated repository maintenance
+# Hypatia Scanner Rules for PanLL — tech-debt regression guards
+#
+# Reconciled 2026-05-17 against the verified tree (see docs/TECHNICAL_DEBT.md).
+#
+# The original v0.2.0 "panic attack" rule set (panll-001..008) was retired:
+# every issue it described is resolved, and its patterns generate false
+# positives against now-correct code — e.g. it flagged the valid
+# `use crate::http_client;`, every `-> String` function, and every
+# `unwrap_or_else(|_| "http://localhost:…")` env fallback. Detecting
+# resolved problems against correct code is worse than no rule.
+#
+# What replaces it: a single, precise regression guard for the one failure
+# mode that actually recurred (commands disabled by commenting them out to
+# force compilation), plus clippy `-D warnings` in CI for everything the
+# old rules tried to approximate (PathBuf misuse, unused doc comments,
+# result-type shape, error handling).
+
+version: "2.0"
 
-version: "1.0"
 rules:
-  # Rule 1: Detect unresolved http_client imports
-  - id: "panll-001"
-    name: "Unresolved http_client Import"
-    description: "Detects unresolved crate::http_client imports that need proper module implementation"
+  # Regression guard for D1: during the panic attack, IPC command handlers
+  # were commented out wholesale to make the crate compile. That is the
+  # specific, recurring pattern worth catching — not "any commented code".
+  - id: "panll-cmd-disabled"
+    name: "Commented-out IPC command registration"
+    description: >
+      A `app.command("…")` registration that has been commented out.
+      This is how functionality was silently dropped to force a build;
+      re-enable it or delete the dead handler and its backing fn.
     severity: "high"
     patterns:
-      - pattern: "use crate::http_client;"
-      - pattern: "use crate::http_client::"
-    remediation:
-      action: "comment"
-      message: "Unresolved http_client import detected. Ensure http_client module exists or implement proper HTTP client infrastructure."
-      suggestions:
-        - "Create http_client.rs module with reqwest-based implementation"
-        - "Add proper ServiceEndpoint struct and HTTP methods"
-        - "Ensure module is properly exported in lib.rs"
-    tags: ["import", "module", "http"]
-
-  # Rule 2: Detect commented-out modules that should be implemented
-  - id: "panll-002"
-    name: "Commented Out Modules"
-    description: "Identifies modules commented out during panic attack that need implementation"
-    severity: "medium"
-    patterns:
-      - pattern: "// mod (\w+);"
-      - pattern: "// \w+::"
+      - pattern: '^\s*//\s*app\.command\('
     remediation:
       action: "ticket"
-      message: "Commented out module detected. This module was disabled during panic attack and needs implementation."
-      suggestions:
-        - "Implement the module or remove references completely"
-        - "Update documentation to reflect module status"
-        - "Add to technical debt backlog"
-    tags: ["module", "technical-debt", "implementation"]
-
-  # Rule 3: Detect improper App handling in Gossamer
-  - id: "panll-003"
-    name: "Improper Gossamer App Handling"
-    description: "Detects incorrect handling of Result<App, Error> types in Gossamer commands"
-    severity: "high"
-    patterns:
-      - pattern: "register_commands(&mut app);"
-      - pattern: "system_tray::init(&app);"
-      - pattern: "app\.run\(\);"
-    context:
-      - "where app is Result<App, Error>"
-    remediation:
-      action: "suggest"
-      message: "Improper App handling detected. App should be unwrapped or handled as Result before use."
-      suggestions:
-        - "Use if let Ok(ref mut app_ok) = app { ... } pattern"
-        - "Properly handle the Result type before passing to functions"
-        - "Add error handling for App initialization failures"
-    tags: ["gossamer", "error-handling", "app"]
-
-  # Rule 4: Detect PathBuf Display trait issues
-  - id: "panll-004"
-    name: "PathBuf Display Trait Misuse"
-    description: "Identifies incorrect usage of PathBuf with Display trait"
-    severity: "high"
-    patterns:
-      - pattern: "\.to_string\(\)"
-      - pattern: "format!\("{}", .*\)"
-    context:
-      - "where type is PathBuf or Path"
-    remediation:
-      action: "replace"
-      message: "PathBuf cannot be directly converted to String. Use to_str() or display() method."
-      suggestions:
-        - "Use path.to_str().unwrap_or(\"\") for string conversion"
-        - "Use path.display() for display formatting"
-        - "Handle potential invalid Unicode paths"
-    tags: ["path", "filesystem", "display"]
-
-  # Rule 5: Detect result type mismatches in commands
-  - id: "panll-005"
-    name: "Command Result Type Mismatch"
-    description: "Detects functions returning String when Result<Value, String> is expected"
-    severity: "high"
-    patterns:
-      - pattern: "result_to_json\(.*\)"
-      - pattern: "-> String"
-    context:
-      - "in command handlers"
-      - "where return type should be Result<Value, String>"
-    remediation:
-      action: "replace"
-      message: "Command should return Result<Value, String> but returns String. Wrap in proper Result type."
-      suggestions:
-        - "Wrap return value in Ok(): Ok(result_to_json(...))"
-        - "Handle errors properly with Err() variant"
-        - "Ensure all command handlers follow consistent return type pattern"
-    tags: ["command", "result", "type-safety"]
-
-  # Rule 6: Detect unused doc comments
-  - id: "panll-006"
-    name: "Unused Documentation Comments"
-    description: "Identifies doc comments that are not attached to any item"
-    severity: "low"
-    patterns:
-      - pattern: "///.*"
-      - pattern: "/\*\*.*\*\/"
-    context:
-      - "not followed by item declaration"
-      - "in commented out sections"
-    remediation:
-      action: "cleanup"
-      message: "Unused documentation comment detected. Either attach to item or remove."
-      suggestions:
-        - "Remove comment if no longer relevant"
-        - "Attach to proper item if documentation is needed"
-        - "Update comment to reflect current code state"
-    tags: ["documentation", "cleanup", "style"]
-
-  # Rule 7: Detect hardcoded service URLs
-  - id: "panll-007"
-    name: "Hardcoded Service URLs"
-    description: "Identifies hardcoded service URLs that should use configuration"
-    severity: "medium"
-    patterns:
-      - pattern: "http://localhost:[0-9]+"
-      - pattern: "localhost:[0-9]+"
-    remediation:
-      action: "configurize"
-      message: "Hardcoded service URL detected. Should use configuration or environment variables."
-      suggestions:
-        - "Use std::env::var() with fallback"
-        - "Add to service registry configuration"
-        - "Make configurable via settings panel"
-    tags: ["configuration", "hardcoding", "best-practice"]
-
-  # Rule 8: Detect improper error handling in commands
-  - id: "panll-008"
-    name: "Improper Command Error Handling"
-    description: "Identifies command handlers that don't properly handle errors"
-    severity: "high"
-    patterns:
-      - pattern: "\.map_err\(.*\)\?"
-      - pattern: "\.unwrap\(\)"
-      - pattern: "\.expect\("""
-    context:
-      - "in command handler functions"
-    remediation:
-      action: "refactor"
-      message: "Improper error handling in command. Should use proper Result propagation."
+      message: >
+        Disabled IPC command detected. Either re-enable it (and its backing
+        function) or remove both plus any now-dead support code. Do not leave
+        commented command handlers in tree.
       suggestions:
-        - "Use ? operator for proper error propagation"
-        - "Return Err(e.to_string()) for command failures"
-        - "Avoid unwrap() and expect() in production code"
-    tags: ["error-handling", "command", "robustness"]
+        - "Re-enable the command and wire its backing function"
+        - "If intentionally removed, delete the handler AND the dead backing fn"
+        - "Record the decision in docs/TECHNICAL_DEBT.md"
+    tags: ["command", "regression", "technical-debt"]
 
-# Remediation Patterns
-remediation_patterns:
-  - id: "result-wrapper"
-    name: "Wrap in Result"
-    description: "Standard pattern for wrapping command results"
-    pattern: |
-      // Before
-      result_to_json(function_call())
-      
-      // After
-      Ok(result_to_json(function_call()))
-    
-  - id: "path-conversion"
-    name: "Safe Path Conversion"
-    description: "Standard pattern for PathBuf to string conversion"
-    pattern: |
-      // Before
-      let path_str = path.to_string();
-      
-      // After
-      let path_str = path.to_str().unwrap_or("");
-    
-  - id: "app-handling"
-    name: "Proper App Handling"
-    description: "Standard pattern for handling Result<App, Error>"
-    pattern: |
-      // Before
-      register_commands(&mut app);
-      app.run();
-      
-      // After
-      if let Ok(ref mut app_ok) = app {
-          register_commands(app_ok);
-          app_ok.run();
-      }
+# Everything the retired rules approximated is now enforced by the compiler
+# and clippy in CI, which is precise where regex patterns were not:
+quality_gate:
+  command: "cargo clippy --all-targets --all-features -- -D warnings"
+  covers:
+    - "PathBuf/Display misuse (was panll-004) — rustc type errors"
+    - "unused / detached doc comments (was panll-006) — clippy::empty_line_after_doc_comments"
+    - "command result-type shape (was panll-005) — rustc type checking of result_to_json"
+    - "error handling (was panll-008) — clippy lints, reviewed per-call"
+  unit_tests: "cargo test --lib   # GTK-free; see lib/bin split"
 
-# Scanner Configuration
 scanner:
   exclude:
     - "**/tests/*"
     - "**/benches/*"
     - "**/examples/*"
     - "**/target/*"
     - "**/node_modules/*"
-  
   include:
-    - "**/src/**/*.rs"
     - "**/src-gossamer/**/*.rs"
 
-# GitBot Fleet Configuration
 gitbot:
-  auto_remediate:
-    - "panll-004"  # PathBuf Display issues
-    - "panll-006"  # Unused doc comments
-    - "panll-007"  # Hardcoded URLs
-  
   create_ticket:
-    - "panll-001"  # http_client implementation needed
-    - "panll-002"  # Commented out modules
-    - "panll-003"  # App handling issues
-    - "panll-005"  # Result type mismatches
-    - "panll-008"  # Error handling issues
-  
+    - "panll-cmd-disabled"
   notification:
-    teams: ["backend", "devops", "qa"]
-    severity_threshold: "medium"
+    teams: ["backend"]
+    severity_threshold: "high"
 
-# Documentation References
 documentation:
   technical_debt: "docs/TECHNICAL_DEBT.md"
-  architecture: "docs/ARCHITECTURE.md"
+  architecture: "docs/architecture/ARCHITECTURE.md"
   contribution: "CONTRIBUTING.md"
-  code_of_conduct: "CODE_OF_CONDUCT.md"
+  code_of_conduct: "CODE_OF_CONDUCT.md"

CHANGELOG.md

@@ -7,18 +7,37 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-### Added (2026-05-11 — Harness schema: Binary Star architecture declaration)
-- **`binary_star` object in panll-harness-v2 schema** — panels can now declare
-  their relationship to the Binary Star architecture (panes A/L/N/W) via
-  four optional fields:
-  - `spans` — panes the panel inhabits (primary state or computation)
-  - `flow` — ordered sequence describing data/control movement
-  - `surfaces_in` — panes where outputs become visible to other panels
-  - `perspective` — vantage point (canonical: observer, meta-observer, actor,
-    sensor, transformer)
+### Changed (2026-05-17 — Tech-debt remediation: lib/bin split)
+- **`[lib] panll` crate extracted** — all GTK-free backend logic
+  (`http_client`, `service_registry`, `settings`, `identity`, `groove`,
+  `llm_coding`, `coprocessor`) moved into a library crate. `main.rs` keeps
+  only `system_tray` (depends on `gossamer_rs`). `cargo test --lib` now runs
+  the unit suite (23 tests) without linking libgossamer/GTK/WebKit.
+- **`coprocessor` wired into the build** — it was orphaned (declared by no
+  crate root, never compiled). Now part of the lib, with real Zig FFI
+  dynamic loading via `libloading 0.8` (`dlopen` + `copro_init`,
+  `copro_dispatch`/`copro_free`), replacing the previous no-op stubs.
 
-  Backward compatible: all fields optional, existing valid v2 manifests remain
-  valid. Unblocks `hyperpolymath/hypatia#197` and `hyperpolymath/hypatia#177`.
+### Added (2026-05-17)
+- Service-registry runtime reconfiguration: `service_list` and
+  `service_set_url` IPC commands; `settings_save` (bulk replace);
+  `llm_coding_system_resources` (host memory + `/proc/stat` CPU sampler).
+- Unit + integration tests for `http_client`, `service_registry`,
+  `llm_coding`, `coprocessor`.
+
+### Removed (2026-05-17)
+- Speculative, never-referenced scaffolding: `WorkspaceLock`,
+  `PendingAction`, `SpawnRequest.task_list`, and the vestigial
+  `service_register`/`service_unregister` command stubs.
+- Stale Tauri references in `coprocessor`/`llm_coding` comments.
+
+### Fixed (2026-05-17)
+- `docs/TECHNICAL_DEBT.md` rewritten from a stale 2024-dated placeholder
+  document into a verified, executed plan; broken `docs/ARCHITECTURE.md`
+  link repointed to `docs/architecture/ARCHITECTURE.md`.
+- `.github/hypatia-rules/panll-v0.2.0-fixes.yml` reconciled (v1 → v2):
+  retired 8 false-positive panic-attack rules, kept one precise regression
+  guard for disabled IPC commands.
 
 ### Fixed (2024-04-15 — v0.2.0 Panic Attack Remediation)
 - **Critical Build Issues** — Resolved 37 compilation errors and warnings during panic attack:

Cargo.lock

@@ -20,6 +20,12 @@ edition = "2021"
 license = "PMPL-1.0-or-later"
 repository = "https://github.com/hyperpolymath/panll"
 
+# Testable logic library — GTK/WebKit-free. `cargo test --lib` runs without
+# linking libgossamer or the GTK/WebKit stack. The bin depends on this lib.
+[lib]
+name = "panll"
+path = "src-gossamer/src/lib.rs"
+
 [[bin]]
 name = "panll-gossamer"
 path = "src-gossamer/src/main.rs"
@@ -55,6 +61,9 @@ libc = "0.2"
 which = "7"
 uuid = { version = "1.22.0", features = ["v4"] }
 
+# Dynamic loading of the Zig coprocessor FFI shared library (Phase 2 data plane)
+libloading = "0.8"
+
 [dev-dependencies]
 tokio = { version = "1", features = ["macros", "rt"] }