Skip to content

Update SPDD specification maintenance artifacts - #52756

Draft
pelikhan with Copilot wants to merge 7 commits into
mainfrom
copilot/spdd-fix-section-numbering
Draft

Update SPDD specification maintenance artifacts#52756
pelikhan with Copilot wants to merge 7 commits into
mainfrom
copilot/spdd-fix-section-numbering

Conversation

Copilot AI commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Addresses daily SPDD findings across threat detection, guard policies, AWF config drift safeguards, and deprecated Safe Outputs documentation. Aligns specification structure, cross-references, and compliance tracking.

  • Threat detection

    • Renumber Deprecation Policy to §5.4.
    • Add v1.0.21 changelog and compatibility-table entry.
    • Add specs/compiler-threat-detection-compliance/README.md mapping CTR rules to T-CTR IDs.
  • Guard policies

    • Restructure proposal content under explicit Approach and Operations sections.
    • Add a Sync Follow-ups entry preserving the new header structure.
  • AWF config safeguards

    • Define consecutive unavailability as persistence through the next scheduled cron trigger; manual/ad hoc runs do not count.
  • Safe Outputs deprecation

    • Add an actionable removal checklist for the 2026-09-21 scratchpad deletion deadline.
    • Cross-link the task from both deprecated and canonical specifications.
    • Synchronize canonical version references to v1.28.3 and correct the scratchpad latest-version URL.
The workflow SHOULD open or update a tracking issue when canonical source
unavailability persists through the next scheduled cron trigger after an
unavailable run; manually rerun or ad hoc runs do not count.

Copilot AI linked an issue Aug 14, 2026 that may be closed by this pull request
10 tasks
Copilot AI and others added 6 commits August 14, 2026 16:21
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix section numbering in threat detection specification Update SPDD specification maintenance artifacts Aug 14, 2026
Copilot AI requested a review from pelikhan August 14, 2026 16:25
@github-actions

Copy link
Copy Markdown
Contributor

PR Triage

  • Category: docs
  • Risk: low
  • Priority: low (score: 25/100)
  • Score breakdown: impact 8/50, urgency 5/30, quality 12/20
  • Recommended action: defer

Automated triage by PR Triage Agent.

Generated by 🔧 PR Triage Agent · auto · 64.3 AIC · ⌖ 2.94 AIC · ⊞ 7.8K ·

@github-actions

Copy link
Copy Markdown
Contributor

Great work on the SPDD specification maintenance! 🎯 This PR addresses daily findings across threat detection, guard policies, config safeguards, and Safe Outputs deprecation with clear, focused changes.

The documentation updates are well-structured:

  • Threat detection: Section renumbering, v1.0.21 changelog, and new compliance mapping (README.md)
  • Guard policies: Restructured proposal with explicit Approach & Operations sections
  • AWF config safeguards: Clear definition of consecutive unavailability
  • Safe Outputs: Actionable removal checklist with deadline and cross-links

All changes are on-topic, cohesive, and properly documented. The draft status with assigned reviewer is appropriate. The PR looks ready to move forward when review feedback is addressed.

Keep it up! 💪

Generated by ✅ Contribution Check · auto · 49.3 AIC · ⌖ 3.46 AIC · ⊞ 8.8K ·

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[spdd] Daily spec work plan - 2026-08-14

2 participants