Skip to content

[spdd] Daily spec work plan - 2026-07-07 #44083

Open
Open
[spdd] Daily spec work plan - 2026-07-07#44083
Assignees
pelikhancopilot-swe-agent
Labels
automationplanningspddspecifications

Description

@github-actions
github-actions
bot
opened on Jul 7, 2026

Summary

Five specs reviewed today across the SPDD pipeline (rotation index 3–7 of 27 total spec files):

  • Effective Tokens (effective-tokens-specification.md) — Status: Deprecated (superseded by AIC); retained for backward-compat
  • Forecast (forecast-specification.md) — Status: Experimental Draft with 3 open Sync follow-ups; needs promotion-gate evidence
  • Frontmatter Hash (frontmatter-hash-specification.md) — Status: Draft; Section 2 field-selection formally deferred to v2.0.0
  • Fuzzy Schedule (fuzzy-schedule-specification.md) — Status: Draft; v1.2.0 weighted slot pool changes recently landed; calendar output schema confirmed complete
  • MCP Scripts (mcp-scripts-specification.md) — Status: Draft v1.1.0; all prior audit items resolved; one open sync task for T-MCP-051 compliance coverage

No critical blockers found. Main themes: ET→AIC migration surface completeness in Forecast spec, deferred field-selection in Frontmatter Hash, and forecast promotion-gate tracking.

Priority Work Queue

P0 – Blocking or regression risk

  • Forecast spec §14 has 2 open [Open] sync items; ET-legacy surfaces need explicit AIC-primary assertion comments

P1 – Active spec debt

  • T-MCP-051 compliance test gap for SN-SCOPE-01..04 secret-scope behavior
  • Frontmatter Hash v2.0.0 prereqs tracker (#31983) needs a spec-side acknowledgment note in §Sync Notes
  • Forecast promotion tracking table needs second and third confirmed production-use entries

P2 – Maintenance / clarity improvements

  • Effective Tokens spec: deprecation banner links to cost-management doc but has no explicit pointer to the migration guide for legacy users
  • Fuzzy Schedule: weighted slot pool change (v1.2.0) not yet reflected in conformance test matrix for calendar output
  • MCP Scripts Go sandbox constraints should cross-link to §10 Safeguards (currently only in Implementation Notes)

SPDD Checklist

/spdd-analysis tasks

  • [A1 — Forecast, P0] In docs/src/content/docs/specs/forecast-specification.md §14 Sync Notes, add an AIC-primary/ET-legacy migration assertion comment under the [Open] item: specify which output fields in pkg/cli/forecast.go are AIC-primary and which remain ET-legacy compatibility-only. Done condition: the [Open] item is replaced with [Resolved] or a concrete tracking issue is linked.
  • [A2 — Forecast, P1] Document a second confirmed production use in the Promotion Tracking table of docs/src/content/docs/specs/forecast-specification.md §Status once a qualifying gh aw forecast run exists. Done condition: table has ≥2 Confirmed rows with valid issue/PR references.
  • [A3 — Frontmatter Hash, P1] In docs/src/content/docs/specs/frontmatter-hash-specification.md §Sync Notes, add a note that issue #31983 is the tracking vehicle for Section 2 deferral; include acceptance criteria directly in the spec so reviewers don't need to visit the issue. Done condition: a Deferral acceptance criteria subsection exists under §Sync Notes.

/spdd-reasons-canvas tasks

  • [RC1 — Forecast, P1] The Safeguards section of forecast-specification.md moved to §10.7; verify that Appendix F stub correctly cross-references §10.7 and add a normative pointer in §14 Sync Notes to the safeguards table. Done condition: §14 includes at least one Safeguards row in the sync mapping table.
  • [RC2 — Effective Tokens, P2] In docs/src/content/docs/specs/effective-tokens-specification.md, strengthen the deprecation caution block to include a direct link to the AIC migration path (e.g., ai-credits-specification.md §Migration). Done condition: deprecation block contains a Migration path: line with a direct spec link.
  • [RC3 — MCP Scripts, P1] In docs/src/content/docs/specs/mcp-scripts-specification.md §13 Sync Notes, add a row for T-MCP-051 compliance coverage against mcp_scripts_renderer_test.go for SN-SCOPE-01 through SN-SCOPE-04. Done condition: sync table has a T-MCP-051 row with the target test file and status [Open] or [Resolved].

/spdd-generate tasks

  • [G1 — MCP Scripts, P1] In pkg/workflow/mcp_scripts_renderer_test.go, add or extend a test named TestMCPScriptsScopeConformance (or similar) to cover SN-SCOPE-01..SN-SCOPE-04 secret-scope behavior assertions, closing the T-MCP-051 gap. Done condition: go test ./pkg/workflow/... -run TestMCPScriptsScopeConformance passes with all four scope norms exercised.
  • [G2 — Fuzzy Schedule, P2] In pkg/parser/schedule_fuzzy_scatter_test.go, verify that the v1.2.0 weighted pool change (622-slot pool from §6.3.1) is covered by a test asserting that BEST slots (02–05 UTC) are selected with 3× higher frequency than OK slots (19–23 UTC) over a large sample. Done condition: test exists and passes deterministically.

/spdd-sync tasks

  • [S1 — Forecast, P0] After any change to pkg/cli/forecast.go AIC/ET output fields, update §14 Sync Notes [Open] item to [Resolved] and link the closing PR. Done condition: no [Open] items remain in §14 for the AIC migration assertion.
  • [S2 — Frontmatter Hash, P1] After issue #31983 milestoning, update §Sync Notes in frontmatter-hash-specification.md to reflect deferral status change. Done condition: §Sync Notes last_run date is updated and deferral status is [Active] or [Completed].

Per-Spec Findings

Effective Tokens Specification (v0.4.0 — Deprecated)

REASONS Canvas:

  • Requirements: Complete — all token class weights and formula requirements are specified.
  • Entities: Complete — token classes, multipliers, execution graph defined.
  • Approach: Adequate for a deprecated spec; deprecation caution present.
  • Structure: Well-structured with conformance levels and appendices.
  • Operations: Aggregation algorithm fully specified in §5.
  • Norms: Present in §14 — adequate.
  • Safeguards: Not present (acceptable given deprecated status).

Key gap: The deprecation block references Cost Management but does not provide a migration path link to ai-credits-specification.md. Legacy users landing on this spec may not find the AIC migration path easily.

Recommended task: Add Migration path: [AI Credits Specification](/gh-aw/specs/ai-credits-specification/) to the caution block.

Forecast Specification (v0.1.0 — Experimental Draft)

REASONS Canvas:

  • Requirements: Strong — command flags, exit codes, and conformance levels are complete.
  • Entities: Well-defined — episode, yield, bootstrap, Monte Carlo trial, projection period.
  • Approach: Sound Monte Carlo + Poisson design; Appendix B/C rationale is thorough.
  • Structure: Good; Appendix F correctly redirects to §10.7 for safeguards.
  • Operations: §4 command interface and §6 data sampling are normative and complete.
  • Norms: §13 covers N-FC-001, N-FC-002, N-FC-003 — adequate.
  • Safeguards: §10.6/10.7 present but the sync table (§14) has no Safeguards row.

Open sync items in §14:

  1. AIC-primary / ET-legacy migration assertions — [Open]
  2. Promotion tracking table needs 2 more confirmed production runs
  3. CI evidence for promotion criterion 3 (both local/remote paths)

Recommended tasks: A1, A2, RC1 above.

Frontmatter Hash Specification (v1.0.0 — Draft)

REASONS Canvas:

  • Requirements: Complete for text-based algorithm; Section 2 field-selection is non-normative (deferred).
  • Entities: BFS traversal, diamond-import, canonical JSON well-defined.
  • Approach: Text-based is authoritative; deferral is formally documented.
  • Structure: Good; safeguards S-1 through S-6 present and verified.
  • Operations: Cross-language consistency protocol in §5.2 is thorough.
  • Norms: None explicitly labelled — norm language is embedded in Implementation Notes.
  • Safeguards: Complete — S-6 sync verification confirmed 2026-05-28.

Key gap: The deferral of §2 to v2.0.0 is documented in Sync Notes but the acceptance criteria are not embedded in the spec — they require visiting issue #31983. Readers without access cannot determine deferral scope.

Recommended tasks: A3 above.

Fuzzy Schedule Specification (v1.2.0 — Draft)

REASONS Canvas:

  • Requirements: Complete grammar ABNF in §3.1; conformance levels defined.
  • Entities: Fuzzy slots, scatter window, weighted pool, avoidance masks — all defined.
  • Approach: FNV-1a hash + weighted 622-slot pool design; well-motivated.
  • Structure: §12 Calendar Output Schema is complete and confirmed (2026-05-26 audit).
  • Operations: Scatter algorithm in §6 is normative; cron generation in §7 is complete.
  • Norms: §13 covers N-DET-001/002 and operator-visible error codes — strong.
  • Safeguards: §8 R-SAFE-003/004/005 present; R-SAFE-005 non-unique hash is underspecified for deterministic offset behavior.

Key gap: v1.2.0 weighted-pool conformance test coverage is not confirmed in sync notes. The 3× BEST-slot frequency claim in §6.3.1 should be verifiable by a unit test.

Recommended tasks: G2 above.

MCP Scripts Specification (v1.1.0 — Draft)

REASONS Canvas:

  • Requirements: Complete — §4 configuration fields, §5 execution requirements all normative.
  • Entities: Tool, transport, sandbox, secret — all defined.
  • Approach: Per-language execution model well-specified in §6.
  • Structure: §13 Sync Notes is the most detailed of the five specs reviewed.
  • Operations: §5.1.1 Operations Ordering normative cross-link in place; retry semantics in §5.7.
  • Norms: §11 norms and 2026-06-01 Norms Audit confirm all gaps resolved.
  • Safeguards: §10 and Appendix D threat model are comprehensive.

Single open item: T-MCP-051 — compliance test coverage for SN-SCOPE-01..04 secret-scope behavior in mcp_scripts_renderer_test.go. Sync Notes call this out but test is not yet confirmed written.

Go sandbox: network/filesystem/secret constraints are well-documented in Implementation Notes but not cross-linked from §10 Safeguards threat model.

Recommended tasks: RC3, G1 above.

Sync Follow-ups

Spec Sync item Action Owner area
forecast-specification.md §14 [Open] AIC/ET migration assertion Link or resolve after forecast.go output-field audit pkg/cli/
forecast-specification.md Promotion tracking ≥3 confirmed runs Add row to §Status table after next qualifying run Spec
frontmatter-hash-specification.md §Sync Notes deferral acceptance criteria Embed criteria from #31983 into spec Spec
mcp-scripts-specification.md §13 T-MCP-051 row Add row + write conformance test pkg/workflow/
fuzzy-schedule-specification.md v1.2.0 weighted pool test coverage Add frequency-distribution unit test pkg/parser/

Context

Files reviewed (rotation index 3–7 of 27):

  1. docs/src/content/docs/specs/effective-tokens-specification.md (v0.4.0, Deprecated)
  2. docs/src/content/docs/specs/forecast-specification.md (v0.1.0, Experimental Draft)
  3. docs/src/content/docs/specs/frontmatter-hash-specification.md (v1.0.0, Draft)
  4. docs/src/content/docs/specs/fuzzy-schedule-specification.md (v1.2.0, Draft)
  5. docs/src/content/docs/specs/mcp-scripts-specification.md (v1.1.0, Draft)

Rotation state: last_index advanced from 2 → 7; next run starts at index 8.

References:
§28882883122

Generated by 📋 Daily SPDD Spec Planner · 64.3 AIC · ⌖ 11.4 AIC · ⊞ 4.8K · ◷

  • expires on Jul 10, 2026, 8:53 AM UTC-08:00

Metadata

Metadata

Assignees

Labels

automationplanningspddspecifications

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions