[pull] main from github:main

.github/aw/serena-tool.md

@@ -60,14 +60,7 @@ imports:
 
 ### 1. Activate Serena First
 
-**Always call activate_project before other Serena tools:**
-
-```javascript
-// activate_project tool
-{
-  "path": "/home/runner/work/gh-aw/gh-aw"
-}
-```
+Always call `activate_project` before other Serena tools, passing the workspace path.
 
 ### 2. Combine with Other Tools
 
@@ -96,35 +89,6 @@ imports:
 cache-memory: true  # Store analysis history
 ```
 
-## Common Patterns
-
-### Pattern 1: Find All Function Usages
-
-```
-1. Use find_symbol to locate function definition
-2. Use find_referencing_code_snippets to find call sites
-3. Analyze patterns
-```
-
-### Pattern 2: Code Quality Analysis
-
-```
-1. Use get_symbols_overview on multiple files
-2. Use find_symbol for similar function names
-3. Use search_for_pattern for duplicate logic
-4. Identify consolidation opportunities
-```
-
-### Pattern 3: Daily Code Analysis
-
-```
-1. Load previous state from cache-memory
-2. Select files using round-robin or priority
-3. Use Serena for semantic analysis
-4. Save findings to cache
-5. Generate improvement tasks
-```
-
 ## Common Pitfalls
 
 ❌ **Using Serena for non-code files** - Use `edit` for YAML/JSON/Markdown
@@ -134,23 +98,4 @@ cache-memory: true  # Store analysis history
 
 ## Supported Languages
 
-Primary languages with full LSP features:
-- `go` (gopls)
-- `typescript` (TypeScript/JavaScript)
-- `python` (jedi/pyright)
-- `ruby` (solargraph)
-- `rust` (rust-analyzer)
-- `java`, `cpp`, `csharp`
-
-See `.serena/project.yml` for complete list (25+ languages).
-
-## Decision Tree
-
-```
-Task requires code semantics/structure?
-├─ NO → Use bash/edit/view
-└─ YES
-    ├─ Simple text search/replace? → Use grep/bash
-    ├─ Config/data files? → Use edit
-    └─ Symbol/structure/semantic patterns? → Use Serena ✅
-```
+Full LSP: `go` (gopls), `typescript`, `python` (jedi/pyright), `ruby` (solargraph), `rust` (rust-analyzer), `java`, `cpp`, `csharp`. See `.serena/project.yml` for full list (25+).

.github/aw/subagents.md

@@ -10,17 +10,7 @@ Inline sub-agents let you define specialised agents directly inside a workflow m
 
 ## Enabling the Feature
 
-Inline sub-agent extraction and restoration steps are enabled by default:
-
-```yaml
----
-engine: copilot
----
-```
-
-> `features.inline-agents` is deprecated and should be removed. Inline sub-agent extraction is always on, so this field is unnecessary.
->
-> `inline-sub-agents: false` is not supported and fails compilation. Remove the field.
+Inline sub-agent extraction is always on — no config needed. The deprecated `features.inline-agents` field and the unsupported `inline-sub-agents: false` field both fail compilation; remove them.
 
 ---
 
@@ -87,12 +77,10 @@ The engine is detected at compile time from the `engine:` field and injected as
 
 ## MCP Access in Sub-Agents
 
-Sub-agents **do not have their own MCP servers**. They run within the parent workflow's agent environment but without independent tool configuration.
-
-For sub-agents to perform useful work they typically need access to the file system and shell. The following tools must be enabled on the parent workflow:
+Sub-agents **do not have their own MCP servers** — they run within the parent's agent environment without independent tool config. To give them file system and shell access, enable on the parent workflow:
 
-- **`cli-proxy: true`** — enables the GitHub CLI proxy so the sub-agent can make authenticated GitHub API calls via `gh`. Strongly recommended for any sub-agent that reads or writes repository content.
-- **`tools.github.mode: gh-proxy`** — routes GitHub API calls through the gh proxy sidecar; required for the sub-agent to operate on private repositories or to use the GitHub MCP toolset.
+- **`cli-proxy: true`** — GitHub CLI proxy for authenticated `gh` calls. Recommended for any sub-agent that reads/writes repo content.
+- **`tools.github.mode: gh-proxy`** — routes GitHub API calls through the gh proxy sidecar; required for private repos or the GitHub MCP toolset.
 
 ```yaml
 ---
@@ -199,6 +187,4 @@ changes. Return a bulleted list, one bullet per file.
 
 - Sub-agents do not support `engine:`, `tools:`, `network:`, or `mcp-servers:` fields — those are stripped at runtime.
 - Sub-agents cannot define their own safe-output jobs.
-- `features.inline-agents` is deprecated and should be removed; inline sub-agent upload/restore is always generated.
-- `inline-sub-agents: false` is rejected at compile time; inline sub-agents cannot be disabled.
 - Sub-agent blocks must appear in the main workflow file body; they are not resolved inside imported shared files.