Restructure softwaredev ways into taxonomy with expanded semantic matching (#30)

* refactor(ways): restructure softwaredev into taxonomy with semantic matching

Reorganize flat softwaredev/ ways into five clusters:
- architecture/ (adr, adr-context, design)
- code/ (errors, performance, quality, security, testing)
- delivery/ (commits, github, migrations, patches, release)
- environment/ (config, debugging, deps, ssh)
- docs/ (docs parent, api child)

Add BM25 description + vocabulary to 11 regex-only ways, expanding
semantic matching from 7 to 18 ways. Fixture tests: 48/54 (0 FP).
Integration tests: 27/31 (0 FP). No regressions from restructure.

Fix ADR tool symlink, update all path references in docs, hook
comments, test harness, and integration tests. Legacy ADR-013
left untouched as historical record.

* test(ways): expand activation test for taxonomy restructure

Add steps 4 (newly-semantic way via BM25) and 5 (co-activation of
related ways) to the live activation test. Update test README with
18-way corpus baseline and new coverage scenarios.

8 test steps covering: regex, established BM25, new BM25, co-activation,
negative control, subagent injection, subagent negative.

* fix(test): correct Step 8 expectation for subagent context inheritance

The subagent negative test was failing because general-purpose subagents
inherit parent conversation context — Performance Way from Step 4 was
visible via context sharing, not SubagentStart injection. The injection
pipeline correctly produced no stash for an irrelevant prompt.

Updated Step 8 to distinguish injection (SubagentStart hook) from
context inheritance (Task tool parent sharing).

Author: aaronsb

commands/test-way.md

@@ -97,7 +97,7 @@ Use the `way-match suggest` command:
 Output is section-delimited (GAPS, COVERAGE, UNUSED, VOCABULARY). Parse and display in a readable format:
 
 ```
-=== Vocabulary Analysis: softwaredev/security ===
+=== Vocabulary Analysis: softwaredev/code/security ===
 
 Gaps (body terms not in vocabulary, freq >= 2):
   parameterized  freq=3

docs/governance.md

@@ -157,9 +157,9 @@ In an enterprise, policy documents and way implementations typically live in sep
 ```
 compliance-repo/              your-claude-config/
 ├── docs/architecture/        ├── hooks/ways/
-│   ├── ADR-150.md           │   ├── softwaredev/commits/way.md
+│   ├── ADR-150.md           │   ├── softwaredev/delivery/commits/way.md
 │   └── ADR-200.md           │   │   (provenance: → ADR-150)
-├── audit-ledger.json        │   └── softwaredev/security/way.md
+├── audit-ledger.json        │   └── softwaredev/code/security/way.md
 └── controls.xlsx            └── governance/
                                  ├── policies/
                                  └── provenance-manifest.json

docs/hooks-and-ways.md

@@ -368,9 +368,9 @@ macro: append    # macro output after static content
 ```
 
 Macros generate dynamic content. Examples:
-- `softwaredev/adr/macro.sh` - Tri-state detection: no tooling, tooling available, tooling installed
-- `softwaredev/quality/macro.sh` - Scans for long files in the project, outputs priority list
-- `softwaredev/github/macro.sh` - Detects solo vs team project, adjusts PR guidance
+- `softwaredev/architecture/adr/macro.sh` - Tri-state detection: no tooling, tooling available, tooling installed
+- `softwaredev/code/quality/macro.sh` - Scans for long files in the project, outputs priority list
+- `softwaredev/delivery/github/macro.sh` - Detects solo vs team project, adjusts PR guidance
 
 **Security**: Project-local macros only run if the project is listed in `~/.claude/trusted-project-macros`.
 
@@ -385,11 +385,11 @@ flowchart TD
     classDef marker fill:#00695C,stroke:#004D40,color:#fff
     classDef result fill:#2E7D32,stroke:#1B5E20,color:#fff
 
-    T["Trigger fires for softwaredev/github"] --> PL
+    T["Trigger fires for softwaredev/delivery/github"] --> PL
 
-    PL{"$PROJECT/.claude/ways/<br/>softwaredev/github/way.md<br/>exists?"}
+    PL{"$PROJECT/.claude/ways/<br/>softwaredev/delivery/github/way.md<br/>exists?"}
     PL -->|yes| USE_P["Use project-local way"]:::project
-    PL -->|no| GL{"~/.claude/hooks/ways/<br/>softwaredev/github/way.md<br/>exists?"}:::global
+    PL -->|no| GL{"~/.claude/hooks/ways/<br/>softwaredev/delivery/github/way.md<br/>exists?"}:::global
     GL -->|yes| USE_G["Use global way"]:::global
     GL -->|no| SKIP["No output"]
 

docs/hooks-and-ways/extending.md

@@ -101,7 +101,7 @@ These are discovered alongside global ways and follow the same matching rules.
 
 A project-local way with the same domain/name path as a global way takes precedence. They share a single marker, so only the project-local version fires.
 
-Example: If a project has `.claude/ways/softwaredev/testing/way.md`, it replaces `~/.claude/hooks/ways/softwaredev/testing/way.md` for that project.
+Example: If a project has `.claude/ways/softwaredev/code/testing/way.md`, it replaces `~/.claude/hooks/ways/softwaredev/code/testing/way.md` for that project.
 
 ### Macros in project-local ways
 

docs/hooks-and-ways/provenance.md

@@ -131,9 +131,9 @@ In an enterprise, policy documents and way implementations typically live in sep
 ```
 compliance-repo/              your-claude-config/
 ├── docs/architecture/        ├── hooks/ways/
-│   ├── ADR-150.md           │   ├── softwaredev/commits/way.md
+│   ├── ADR-150.md           │   ├── softwaredev/delivery/commits/way.md
 │   └── ADR-200.md           │   │   (provenance: → ADR-150)
-├── audit-ledger.json        │   └── softwaredev/security/way.md
+├── audit-ledger.json        │   └── softwaredev/code/security/way.md
 └── controls.xlsx            └── provenance-manifest.json
 ```
 

docs/hooks-and-ways/stats.md

@@ -7,7 +7,7 @@ You can't manage what you can't see. The ways system logs every firing event and
 Every time a way fires, `log-event.sh` appends a line to `~/.claude/stats/events.jsonl`:
 
 ```json
-{"ts":"2026-02-05T19:00:34Z","event":"way_fired","way":"softwaredev/commits","domain":"softwaredev","trigger":"bash","scope":"agent","project":"/home/you/myproject","session":"abc-123"}
+{"ts":"2026-02-05T19:00:34Z","event":"way_fired","way":"softwaredev/delivery/commits","domain":"softwaredev","trigger":"bash","scope":"agent","project":"/home/you/myproject","session":"abc-123"}
 ```
 
 Session start events are also logged. For teammates, the team name is included:
@@ -39,8 +39,8 @@ Top ways:
   meta/todos                      96  ████████████████████
   meta/memory                     96  ████████████████████
   meta/knowledge                  30  ██████
-  softwaredev/commits             19  ███
-  softwaredev/design              18  ███
+  softwaredev/delivery/commits    19  ███
+  softwaredev/architecture/design 18  ███
 
 By scope:
   agent        319

docs/scripts/adr

@@ -1 +1 @@
-../../hooks/ways/softwaredev/adr/adr-tool
+../../hooks/ways/softwaredev/architecture/adr/adr-tool

hooks/ways/check-bash-pre.sh

@@ -9,7 +9,7 @@
 #                         │  keywords match │
 #                         └─────────────────┘
 #
-# Ways are nested: domain/wayname/way.md (e.g., softwaredev/github/way.md)
+# Ways are nested: domain/wayname/way.md (e.g., softwaredev/delivery/github/way.md)
 # Multiple ways can match a single command - CONTEXT accumulates
 # all matching way outputs. Markers prevent duplicate content.
 # Output is returned as additionalContext JSON for Claude to see.
@@ -33,7 +33,7 @@ scan_ways() {
 
   # Find all way.md files recursively
   while IFS= read -r -d '' wayfile; do
-    # Extract way path relative to ways dir (e.g., "softwaredev/github")
+    # Extract way path relative to ways dir (e.g., "softwaredev/delivery/github")
     waypath="${wayfile#$dir/}"
     waypath="${waypath%/way.md}"
 

hooks/ways/check-file-pre.sh

@@ -8,7 +8,7 @@
 # └───────────────────────┘     │  if files match │     └──────────────┘
 #                               └─────────────────┘
 #
-# Ways are nested: domain/wayname/way.md (e.g., softwaredev/github/way.md)
+# Ways are nested: domain/wayname/way.md (e.g., softwaredev/delivery/github/way.md)
 # Multiple ways can match a single file path - CONTEXT accumulates
 # all matching way outputs. Markers prevent duplicate content.
 # Output is returned as additionalContext JSON for Claude to see.
@@ -31,7 +31,7 @@ scan_ways() {
 
   # Find all way.md files recursively
   while IFS= read -r -d '' wayfile; do
-    # Extract way path relative to ways dir (e.g., "softwaredev/github")
+    # Extract way path relative to ways dir (e.g., "softwaredev/delivery/github")
     waypath="${wayfile#$dir/}"
     waypath="${waypath%/way.md}"
 

hooks/ways/check-prompt.sh

@@ -9,7 +9,7 @@
 #                          │  semantic match │
 #                          └─────────────────┘
 #
-# Ways are nested: domain/wayname/way.md (e.g., softwaredev/github/way.md)
+# Ways are nested: domain/wayname/way.md (e.g., softwaredev/delivery/github/way.md)
 # Matching is ADDITIVE: pattern (regex/keyword) and semantic are OR'd.
 # Semantic matching degrades: BM25 binary → gzip NCD → skip.
 # Project-local ways are scanned first (and take precedence).
@@ -45,7 +45,7 @@ scan_ways() {
 
   # Find all way.md files recursively
   while IFS= read -r -d '' wayfile; do
-    # Extract way path relative to ways dir (e.g., "softwaredev/github")
+    # Extract way path relative to ways dir (e.g., "softwaredev/delivery/github")
     waypath="${wayfile#$dir/}"
     waypath="${waypath%/way.md}"