fix(library): address Copilot review comments on marketing job

- Remove external convention references (process.notes, tool.zk-notes,
  ZK_NOTEBOOK_DIR) from README and AGENTS.md for portability
- Use platform-neutral "sub-agents" wording instead of "Agent tool"
- Fix manifest template to reference research job's README.md output
- Fix cca_analyze_patterns to read README.md files from manifest

Skipped: CLAUDE.md symlink comment (incorrect — it IS a symlink),
step duplication (known trade-off, non-blocking)

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

Author: ncrmro

library/jobs/README.md

@@ -75,11 +75,11 @@ Library jobs that produce durable outputs (reports, research, decisions) should
 
 **How it works in practice**:
 
-1. The job's `discover_context` step checks `NOTES_DIR` or `ZK_NOTEBOOK_DIR` and reads the AGENTS.md there.
-2. The agent's platform conventions (e.g., `process.notes`, `tool.zk-notes`) provide the mechanics for note creation.
+1. The job's `discover_context` step checks for a user-configured notes directory (e.g., via `NOTES_DIR`) and reads the AGENTS.md there when available.
+2. The user's environment-specific conventions provide the mechanics for note creation.
 3. If no notes directory exists, the job falls back to `.deepwork/tmp/` with plain markdown.
 
-This separation means the same library job works for a Keystone user with a zk notebook, an Obsidian user, or someone with no notes system at all.
+This separation means the same library job works for users with different note-taking setups, as well as someone with no notes system at all.
 
 ## Structure
 

library/jobs/marketing/AGENTS.md

@@ -54,8 +54,8 @@ to `.deepwork/tmp/` only if no notes directory exists.
 This job does not embed note creation mechanics (zk commands, frontmatter
 format, tag conventions) because those vary by user setup. The user's notes
 repo AGENTS.md and the agent's platform conventions are the source of truth for
-how to create notes. See `process.notes` and `tool.zk-notes` for the canonical
-rules if available in the agent's instruction context.
+how to create notes. Follow the user's notes-directory conventions and any
+applicable instructions available in the agent's instruction context.
 
 ## Quality review learnings
 

library/jobs/marketing/job.yml

@@ -275,8 +275,8 @@ workflows:
              - `inputs`: `topic` = "[Competitor Name] content strategy: [content focus areas]",
                `type` = "competitive", `depth` = "quick"
 
-             Launch all competitors in parallel using the Agent tool — one
-             agent per competitor, each calling `start_workflow` independently.
+             Launch all competitors in parallel by spawning sub-agents — one
+             per competitor, each calling `start_workflow` independently.
 
              The research job produces `sources.md`, `analysis.md`, and
              `README.md` per competitor — the README serves as the competitor
@@ -311,8 +311,8 @@ workflows:
 
           | Competitor | Report path | Key finding |
           |-----------|-------------|-------------|
-          | [Name 1]  | [path/to/competitor_report.md] | [One-line summary] |
-          | [Name 2]  | [path/to/competitor_report.md] | [One-line summary] |
+          | [Name 1]  | [path/to/research/README.md] | [One-line summary] |
+          | [Name 2]  | [path/to/research/README.md] | [One-line summary] |
 
           ## Failures (if any)
 
@@ -347,7 +347,7 @@ workflows:
 
           1. **Read inputs**
              - Read competitor_reports_manifest.md to find all report paths.
-             - Read each competitor_report.md file referenced in the manifest.
+             - Read each report file (README.md) referenced in the manifest.
 
           2. **Cross-competitor analysis**