🚀🧑‍💻 - 3.5.6 - Setup dogfooding and SDD draft recovery #543

Release Type

Patch

Release Version

3.5.6

Changelog

• Fix recommendation-mode setup asking for Checks access unavailable to fine-grained operator PATs ([#536] 🐛 - Setup recommend mode requires Checks access unavailable to fine grained PATs #537 / 🐛🧑‍💻 - Setup recommend mode requires Checks access unavailable to fine grained PATs #536).
• Use absolute shared documentation links in generated repository guidance and safely upgrade setup-owned legacy guides ([#539] 🐛 - bug generated agent guidance links to documentation missing in target repositories #540 / 🐛🧑‍💻 - bug generated agent guidance links to documentation missing in target repositories #539).
• Complete complex pre-branch SDD generation using a compatible Codex native schema while preserving full local acceptance, and identify provider output-token-limit failures safely ([#541] 🐛 - bug pre branch SDD drafting fails after successful analysis with an unclassified agent exit #542 / 🐛🧑‍💻 - bug pre branch SDD drafting fails after successful analysis with an unclassified agent exit #541).

Additional Context

This patch is needed so the live issue/comment workflows, which execute the local Action from master, can use the reviewed SDD correction and resume setup feature #538 through normal Action-owned SDD/branch publication.

Source release baseline: v3.5.5, master 29270b2. #537, #540 and #542 are merged into develop. Verified source commit: 95d64ff. Every executed check on final #542 head b16f55e passed, including hosted Linux/macOS/Windows, full coverage, package smoke, Bugbot and RepoWise. The maintainer explicitly authorized merging #542 and publishing v3.5.6 in this session. Start this release after #542 is merged and all CI is green. Follow the existing release issue, managed branch/PR, validation, master integration, version tag and package publication lifecycle without bypassing protections.

This release contains the reviewed fixes. The organization-reuse and multi-repository feature implementation remains on #538, and the platform vulnerability work remains separate.