-
Notifications
You must be signed in to change notification settings - Fork 1
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#799 In CorvidLabs/spec-sync;
- Status: Open.#798 In CorvidLabs/spec-sync;
change check rejects unchanged Git LFS assets through the whole-workspace evidence digest
area:product-bugRuntime or CLI behavior is incorrectRuntime or CLI behavior is incorrectbugSomething isn't workingSomething isn't workingpriority:p2Important but not immediately release-blockingImportant but not immediately release-blockingscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#789 In CorvidLabs/spec-sync;fix: generated pre-commit diagnostic executes shell substitutions in project paths
area:product-bugRuntime or CLI behavior is incorrectRuntime or CLI behavior is incorrectarea:securityIntegrity, authentication, supply-chain, or secret-handling riskIntegrity, authentication, supply-chain, or secret-handling riskarea:uxMessages, output, or next actions mislead or frustrateMessages, output, or next actions mislead or frustrateimpact:user-facingCan affect an end user or repository operator directlyCan affect an end user or repository operator directlypriority:p1Highest-impact or release-blocking riskHighest-impact or release-blocking riskscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#782 In CorvidLabs/spec-sync;check --fix: subsection boundary and multi-table edge cases in the code-aware table scanner
area:test-coverageTests, verification, coverage, or lint coverage gapTests, verification, coverage, or lint coverage gaparea:uxMessages, output, or next actions mislead or frustrateMessages, output, or next actions mislead or frustrateimpact:developer-experienceAffects authors, maintainers, or local workflowsAffects authors, maintainers, or local workflowspriority:p2Important but not immediately release-blockingImportant but not immediately release-blockingresolution:partialRelated work landed but meaningful residual work remainsRelated work landed but meaningful residual work remainsscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#768 In CorvidLabs/spec-sync;the drift check cannot see a requirement that no longer describes the code, whether it lost its implementation or was contradicted by its successor
area:governanceLifecycle, approval, adoption, or release-policy behaviorLifecycle, approval, adoption, or release-policy behaviorarea:product-bugRuntime or CLI behavior is incorrectRuntime or CLI behavior is incorrectimpact:developer-experienceAffects authors, maintainers, or local workflowsAffects authors, maintainers, or local workflowspriority:p2Important but not immediately release-blockingImportant but not immediately release-blockingresolution:partialRelated work landed but meaningful residual work remainsRelated work landed but meaningful residual work remainsscope:legacy-validLegacy or migration path remains supported and affectedLegacy or migration path remains supported and affectedscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#728 In CorvidLabs/spec-sync;the merge-before-finalize warning only reaches operators who run the verb that prints it
area:governanceLifecycle, approval, adoption, or release-policy behaviorLifecycle, approval, adoption, or release-policy behaviorarea:product-bugRuntime or CLI behavior is incorrectRuntime or CLI behavior is incorrectarea:uxMessages, output, or next actions mislead or frustrateMessages, output, or next actions mislead or frustrateimpact:user-facingCan affect an end user or repository operator directlyCan affect an end user or repository operator directlypriority:p1Highest-impact or release-blocking riskHighest-impact or release-blocking riskscope:legacy-validLegacy or migration path remains supported and affectedLegacy or migration path remains supported and affectedscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#712 In CorvidLabs/spec-sync;change check cannot fail for anything CI gates on: clippy is missing from the verification command set
area:ciRemote or local CI gate/workflow mismatchRemote or local CI gate/workflow mismatcharea:test-coverageTests, verification, coverage, or lint coverage gapTests, verification, coverage, or lint coverage gapimpact:developer-experienceAffects authors, maintainers, or local workflowsAffects authors, maintainers, or local workflowsimpact:maintainerPrimarily affects CI, release, or repository operatorsPrimarily affects CI, release, or repository operatorspriority:p1Highest-impact or release-blocking riskHighest-impact or release-blocking riskscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#708 In CorvidLabs/spec-sync;a second wall-clock flaky gate: the coverage-barrier tests miss their deadline under full-suite load
area:ciRemote or local CI gate/workflow mismatchRemote or local CI gate/workflow mismatcharea:test-coverageTests, verification, coverage, or lint coverage gapTests, verification, coverage, or lint coverage gapimpact:developer-experienceAffects authors, maintainers, or local workflowsAffects authors, maintainers, or local workflowsimpact:maintainerPrimarily affects CI, release, or repository operatorsPrimarily affects CI, release, or repository operatorspriority:p2Important but not immediately release-blockingImportant but not immediately release-blockingscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#707 In CorvidLabs/spec-sync;the scoped-review descendant walk fails closed forever after a squash, and its guarantee is unavailable rather than violated
area:governanceLifecycle, approval, adoption, or release-policy behaviorLifecycle, approval, adoption, or release-policy behaviorarea:securityIntegrity, authentication, supply-chain, or secret-handling riskIntegrity, authentication, supply-chain, or secret-handling riskimpact:developer-experienceAffects authors, maintainers, or local workflowsAffects authors, maintainers, or local workflowsimpact:maintainerPrimarily affects CI, release, or repository operatorsPrimarily affects CI, release, or repository operatorspriority:p1Highest-impact or release-blocking riskHighest-impact or release-blocking riskresolution:partialRelated work landed but meaningful residual work remainsRelated work landed but meaningful residual work remainsscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#694 In CorvidLabs/spec-sync;ship-status advertises
check --commitfromaccepted, where check's own state machine rejects itarea:product-bugRuntime or CLI behavior is incorrectRuntime or CLI behavior is incorrectarea:uxMessages, output, or next actions mislead or frustrateMessages, output, or next actions mislead or frustrateimpact:developer-experienceAffects authors, maintainers, or local workflowsAffects authors, maintainers, or local workflowsimpact:user-facingCan affect an end user or repository operator directlyCan affect an end user or repository operator directlypriority:p2Important but not immediately release-blockingImportant but not immediately release-blockingresolution:partialRelated work landed but meaningful residual work remainsRelated work landed but meaningful residual work remainsscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#690 In CorvidLabs/spec-sync;predecessor and successor archive refusals cite the same invariant and name each other, and neither says the counterpart is blocked too
area:governanceLifecycle, approval, adoption, or release-policy behaviorLifecycle, approval, adoption, or release-policy behaviorarea:securityIntegrity, authentication, supply-chain, or secret-handling riskIntegrity, authentication, supply-chain, or secret-handling riskimpact:developer-experienceAffects authors, maintainers, or local workflowsAffects authors, maintainers, or local workflowsimpact:maintainerPrimarily affects CI, release, or repository operatorsPrimarily affects CI, release, or repository operatorspriority:p1Highest-impact or release-blocking riskHighest-impact or release-blocking riskresolution:partialRelated work landed but meaningful residual work remainsRelated work landed but meaningful residual work remainsscope:specsync-6Applies to current SpecSync 6 behavior or release contractApplies to current SpecSync 6 behavior or release contractStatus: Open.#688 In CorvidLabs/spec-sync;