Align 1513 deferral tiers and Issue 6 Zod/hot-reload scope (follow-up to #4069)

[mareklibra]

Labels: ready-to-code
Depends on: #4069 (RHDHPLAN-1505 staging / frontend / 1513 deferral docs)
RHIDP Stories: n/a (docs consistency follow-up)
Feature: RHDHPLAN-1505 — staging plan maintenance

Fix two internal-consistency gaps left after PR #4069 review so fullsend agents reading the staging plan and 1513 deferral analysis do not mis-schedule work or invent boost.connectors Zod/hot-reload for MCP/RHOAI/OCI.

1. Deferral tier drift — RHDHPLAN-1513-defer-from-2-1-staging-and-jira-impact.md still uses pre-reclassification tiers (Issues 23/24/26 as Tier 2; Tier 1 “1 of 15”; Tier 2 “3 of 7”). Authoritative staging in rhdhplan1505-1-staged-issues.md has Issues 23, 24, 26 in Tier 1 (Tier 1 = 18, Tier 2 = 4). Safe/blocked totals (21/8) stay correct; update tier labels, footprint shares, and safe-section tables only.

2. Issue 6 Zod scope over-promise — Issue 6 / Connector Config — Zod Schemas and RuntimeConfigResolver Extension (issue 6 of 29) #4044 says AI catalog connectors (MCP Registry, RHOAI, OCI) “will add their own Zod schemas when created in Issues 7–16,” but those issues only define ai-catalog.providers.* / API-response Zod. Issue 22 (Hot-Reload Propagation to Active Connectors (issue 22 of 29) #4060) and Issue 28 (Connector Config Admin UI (issue 28 of 29) #4066) remain Jira/GitHub/GitLab boost.connectors.* only. Soften the staging + Connector Config — Zod Schemas and RuntimeConfigResolver Extension (issue 6 of 29) #4044 wording to match actual 2.1 scope (do not add new MCP/RHOAI/OCI boost.connectors schema/hot-reload tasks in this issue).

Tasks

1. Align 1513 deferral doc with current staging tiers

Edit workspaces/boost/specifications/JIRA-analysis/RHDHPLAN-1513-defer-from-2-1-staging-and-jira-impact.md:

• 1.1 Epic RHIDP-15331 story table: Issue 26 Start Tier / Complete Tier → Tier 1 (not Tier 2) for RHIDP-15335 complete, RHIDP-15336, RHIDP-15339
• 1.2 Prose under that table: force-sync routes in Issue 26 are Tier 1 (not Tier 2)
• 1.3 1513 Footprint Across Tiers table:
  • Tier 0: Issues 4, 5, 6 — 3 of 7 (unchanged)
  • Tier 1: Issues 22, 26 — 2 of 18
  • Tier 2: Issues 27, 28 — 2 of 4
  • Total: 7 of 29 (unchanged)
• 1.4 Issues Safe to Run sections:
  • Move Issues 23 and 24 from the Tier 2 safe table into the Tier 1 safe table
  • Tier 1 header: safe set excludes Issues 22 and 26 (depends on Issues 6 and 5) → 16 of 18
  • Tier 2 safe table: Issue 25 only (1 of 4)
• 1.5 Blocked list: label Issue 26 as Tier 1; keep Issues 27–29 as Tier 2
• 1.6 Confirm totals still read 21 of 29 safe / 8 blocked; only tier bookkeeping changes

2. Clarify Issue 6 boost.connectors Zod / hot-reload scope

Edit workspaces/boost/specifications/JIRA-analysis/rhdhplan1505-1-staged-issues.md Issue 6 description and sync GitHub #4044 in lockstep:

• 2.1 Replace the sentence that AI catalog connectors “will add their own Zod schemas when created in Issues 7–16” with explicit 2.1 scope:
  • boost.connectors.* Zod schemas + RuntimeConfigResolver / hot-reload / admin UI cover existing Jira, GitHub, and GitLab entity-provider connectors (Issues 6, 22, 28)
  • MCP Registry, RHOAI, and OCI use ai-catalog.providers.<id>.* startup registration (YAML-only enabled); runtime boost.connectors Zod/hot-reload for those connectors is out of scope for this staging plan (follow-up later if needed)
• 2.2 Keep the existing Config note (ai-catalog.providers.<id>.enabled vs boost.connectors.<id>.enabled) unchanged
• 2.3 Do not add new tasks under Issues 7–16, 22, or 28 for AI-connector boost.connectors schemas
• 2.4 Update GitHub issue Connector Config — Zod Schemas and RuntimeConfigResolver Extension (issue 6 of 29) #4044 body to match the revised Issue 6 description

Specifications

• workspaces/boost/specifications/JIRA-analysis/RHDHPLAN-1513-defer-from-2-1-staging-and-jira-impact.md
• workspaces/boost/specifications/JIRA-analysis/rhdhplan1505-1-staged-issues.md (Issue 6)
• GitHub Connector Config — Zod Schemas and RuntimeConfigResolver Extension (issue 6 of 29) #4044 (lockstep with Issue 6 text)
• Cross-check only (no edits required unless drift found): rhdhplan1505-1-staged-issues.md Tier headers / dependency graph (Tier 1 = 18 incl. 23/24/26; Tier 2 = 4); Issues 22 (Hot-Reload Propagation to Active Connectors (issue 22 of 29) #4060) and 28 (Connector Config Admin UI (issue 28 of 29) #4066) remain Jira/GitHub/GitLab-scoped

[mareklibra]

/fs-triage

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:44 AM UTC · Completed 8:48 AM UTC
Commit: d755095 · View workflow run →

[fullsend-ai-triage]

Triage Summary

This is a well-specified documentation consistency follow-up with two distinct tasks. The dependency on PR #4069 is already resolved (merged).

Task 1 — Deferral Tier Alignment

The RHDHPLAN-1513 deferral analysis doc still uses pre-reclassification tier labels. Issues 23, 24, and 26 need to move from Tier 2 to Tier 1 labels throughout the document, with corresponding updates to the footprint table (Tier 1: 2 of 18, Tier 2: 2 of 4) and safe/blocked sections (Tier 1 safe: 16 of 18, Tier 2 safe: Issue 25 only at 1 of 4). Grand totals (21/29 safe, 8 blocked) remain unchanged.

Task 2 — Issue 6 Zod Scope Clarification

Issue 6's description over-promises boost.connectors Zod/hot-reload for AI catalog connectors (MCP Registry, RHOAI, OCI). The actual 2.1 scope limits boost.connectors to Jira/GitHub/GitLab only; AI catalog connectors use ai-catalog.providers.<id>.* startup registration. Both rhdhplan1505-1-staged-issues.md and GitHub issue #4044 need to be updated in lockstep.

Verification

Post-edit checks:
- Tier counts: Tier 0 = 3/7, Tier 1 = 2/18, Tier 2 = 2/4, Total = 7/29
- Issues 23/24 in Tier 1 safe table (not Tier 2)
- Tier 1 safe = 16/18, Tier 2 safe = 1/4 (Issue 25 only)
- Issue 26 labeled Tier 1 in blocked list; 27-29 remain Tier 2
- Grand totals: 21/29 safe, 8/29 blocked (unchanged)
- Issue 6 text: no boost.connectors claims for MCP/RHOAI/OCI
- GitHub #4044 body matches revised Issue 6 description

---

Next steps:

• /fs-code — agent creates a PR to implement this issue
• /fs-code <your instruction> — agent implements with your specific guidance

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 8:49 AM UTC · Completed 8:57 AM UTC
Commit: d755095 · View workflow run →

[mareklibra]

/fs-code