Repository navigation
[spdd] Daily spec work plan - 2026-10-19 #70287
Description
Summary
Reviewed 5 specification files (rotation indexes 10-14). Findings: the OTel spec is large (~68 KB) and benefits from a canvas-style safeguards/norms audit; the ESLint factory model has many stated abstractions that need explicit sync notes; fixtures and compliance READMEs need traceability checks against their parent specs.
Priority Work Queue
- P0: Audit
specs/otel-observability-spec.mdsafeguards (missing-value policy, header handling, trust boundaries). - P1: Sync
specs/eslint-factory/README.mdabstractions with executable code; verify test-ID traceability inspecs/awf-config-sources-compliance/README.mdandspecs/forecast-compliance-fixtures/README.md. - P2: Document intent and fixture-only status in
specs/workflow-security/fixtures/cross-repo.md.
SPDD Checklist
- (
/spdd-analysis, P0) Inspecs/otel-observability-spec.mdlist ambiguous MUST/SHOULD requirements in sections 5-7. Done: ambiguity list with section refs is posted in a comment. - (
/spdd-reasons-canvas, P0) Inspecs/otel-observability-spec.mdadd a Safeguards/Norms summary covering header secrecy and missing-value policy. Done: both sections have explicit MUST-level rules. - (
/spdd-generate, P1) Inpkg/workflow/add or confirm tests for OTel endpoint/allowlist rules (sections 5.2, 5.7). Done: each rule maps to a named test. - (
/spdd-analysis, P1) Inspecs/eslint-factory/README.mdenumerate modeled-vs-native gaps (dispatch slots, fairness, readback). Done: a table lists each gap with owner status. - (
/spdd-generate, P1) Inspecs/awf-config-sources-compliance/README.mdverify T-DR-001..011 exist inpkg/workflow/awf_config_drift_test.goandawf_config_safeguards_formal_test.go. Done: no test ID lacks an implementation. - (
/spdd-reasons-canvas, P1) Inspecs/forecast-compliance-fixtures/README.mdconfirm retired T-FC-041..044 are absent from the parent spec. Done: parent spec and README agree. - (
/spdd-generate, P2) Inspecs/workflow-security/fixtures/cross-repo.mdadd a header comment/README note stating the fixture purpose and expected compiled model. Done: purpose is documented. - (
/spdd-sync, P2) Inspecs/add a short changelog note per touched spec. Done: each edited spec has a dated sync entry.
Per-Spec Findings
specs/otel-observability-spec.md
Goals: standard OTLP observability for workflows. Risks: very large spec, header/secret exposure, endpoint allowlisting. Canvas gaps: Safeguards and Norms are spread across sections; Operations ordering for flush/shutdown should be checked.
specs/eslint-factory/README.md
Bounded formal model with explicit non-claims. Gaps: two-Work projection, no automatic DAG, scenario-assumed output bounds. Needs sync notes against native tests.
specs/awf-config-sources-compliance/README.md
DriftRecord test IDs T-DR-001..011 map to Go tests. Verify tests exist and the escalation owner fallback is defined in the spec.
specs/forecast-compliance-fixtures/README.md
Episode requirements retired; T-FC-056 replaces the yield predicate. Check for stale references in the forecast spec.
specs/workflow-security/fixtures/cross-repo.md
A workflow fixture with cross-repo checkout, GitHub App, and bash allowlist. Lacks documentation of the expected compiled security model.
Sync Follow-ups
- Re-run spec-to-test traceability after any spec edit (
specs/,pkg/workflow/). - Update the ESLint factory README when
eslint_factory_portfolio.cjsbehavior changes. - Keep the forecast spec in
docs/src/content/docs/specs/aligned with the fixtures README.
Context
- Files reviewed: specs/workflow-security/fixtures/cross-repo.md, specs/eslint-factory/README.md, specs/forecast-compliance-fixtures/README.md, specs/otel-observability-spec.md, specs/awf-config-sources-compliance/README.md
- Rotation index: last_index=14 (previous 9)
- Run URL: https://github.com/github/gh-aw/actions/runs/39281271989
Generated by 📋 Daily SPDD Spec Planner · copilot · auto · 15.2 AIC · ⌖ 0.626 AIC · ⊞ 7.8K · ◷
- expires on Oct 22, 2026, 8:00 AM UTC-08:00
Activity
github-actions commentedon Oct 22, 2026
This issue was automatically closed because it expired on 2026-10-22T16:00:20.439Z.