forgedock 1.0.10 → 1.0.11

package/commands/work-on.md

@@ -1006,15 +1006,16 @@ PR #${PR_NUMBER} created targeting \`{PR_BASE}\`. Invoking /review-pr with --aut
 
 Large-context sessions that accumulated significant build history cause review-pr to hit the token limit mid-review. Check the accumulated context before delegating:
 
-- If the build changed **≥6 files** OR this agent has made **≥20 Skill invocations** since it started: invoke `work-on/review` as a fresh sub-agent (via `Skill(skill="work-on/review", args="...")`) rather than calling review-pr directly. The sub-agent starts with a clean context window.
+- If the build changed **≥10 files** OR this agent has made **≥20 Skill invocations** since it started: invoke `work-on/review` as a fresh sub-agent (via `Skill(skill="work-on/review", args="...")`) rather than calling review-pr directly. The sub-agent starts with a clean context window.
 - Otherwise (small build, few skill calls): invoke review-pr directly as below.
+- **Fallback**: if `work-on/review` is not available (partial install), invoke review-pr directly regardless of file count and add a note that context may be large.
 
-**Direct invocation** (small builds — <6 changed files AND <20 Skill invocations):
+**Direct invocation** (small builds — <10 changed files AND <20 Skill invocations):
 ```
 Skill(skill="review-pr", args="{PR_NUMBER} --auto-merge --issue {NUMBER} --base {PR_BASE} --gh-flag {GH_FLAG}")
 ```
 
-**Sub-agent invocation** (large builds — ≥6 changed files OR ≥20 Skill invocations):
+**Sub-agent invocation** (large builds — ≥10 changed files OR ≥20 Skill invocations):
 ```
 Skill(skill="work-on/review", args="{NUMBER} --repo {GH_REPO} --gh-flag {GH_FLAG} --worktree {WORKTREE_PATH} --branch {BRANCH} --base {PR_BASE}")
 ```

package/docs/CONFIG.md

@@ -472,6 +472,25 @@ Colors are grouped by semantic meaning:
 
 ---
 
+## `marketing` (OPTIONAL)
+
+Controls opt-in growth features such as 'Powered by ForgeDock' footers on PR descriptions created by the pipeline.
+
+> **Note**: `pr_footer` injection requires future pipeline support in `/work-on`. Setting `pr_footer: true` today has no effect — it is a configuration interface that will be activated when the feature ships. When implemented, the pipeline will append a one-line footer to every PR body it creates.
+
+```yaml
+marketing:
+  pr_footer: false
+```
+
+| Field | Type | Required | Default | Description |
+|-------|------|----------|---------|-------------|
+| `pr_footer` | boolean | No | `false` | When `true`, the pipeline appends a 'Powered by ForgeDock' footer link to every PR description it creates. Opt-in only — non-intrusive one-line footer, not a banner. Requires pipeline support (not yet implemented). |
+
+**Commands that use this section**: `work-on` (Phase 4 PR creation — when `pr_footer: true`)
+
+---
+
 ## Config Reading Conventions
 
 ForgeDock commands use two accepted patterns for reading `forge.yaml`: