Skip to content

[Change] Native Windows x86-64 Code Review capsule with project-driven preparation #495

Closed as not planned

Description

@djm81

Extend Code Review to native Windows x86-64 using the project configuration and preparation contract delivered by #460. This is a deferred follow-up, not part of the current Linux x86-64/macOS ARM64 delivery.

Parent: Feature #163, “Validation Evidence And Governance Runtime Follow-Ups” (Epic #162). OpenSpec: code-review-windows-native-platform-execution.

Scope:

  • Preserve ProjectPlan discovery, explicit configuration precedence, runtime inspect/prepare, automatic runtime acquisition and project-driven preparation without publisher entries for customer projects.
  • Run authentic pinned pip, Hatch, uv and Poetry on disposable snapshots. Separate sealed analyzers, acquisition, build hooks, project imports/plugins/tests and compatible native extensions.
  • Prove a Windows execution boundary before admission: startup ownership, managed children, denied unauthorized filesystem/network/descriptor access, enforced resources, five-second cleanup and 100 repetitions of lifecycle races. Assess native Windows mechanisms against the shared contract; do not declare a mechanism sufficient merely because it exists.
  • Deliver verified Windows/ABI artifacts, PE dependency inventory, atomic locally built project caches and verified offline reuse. Preserve report/evidence compatibility and project-origin-v1 pytest restrictions.
  • Require all ten analyzers and the full four-manager corpus on matching-architecture Windows VMs or physical machines, under an ordinary user with normal protections. Default hosted Windows administrator/UAC-disabled settings alone do not establish that installation acceptance.
  • Optional UTM x86-64 guests on Apple Silicon support debugging; emulation is supplemental. ARM64 Windows running translated x86-64 applications, WSL and Docker do not establish native Windows x86-64 acceptance.
  • Publisher/module signing keys stay in CI/CD. No paid publisher membership, Docker, hypervisor, administrator account or customer SDK is a runtime prerequisite. Verify the actual download/installation route before promising that behavior.

Dependency direction: #460 blocks this follow-up. This follow-up does not block #460 or existing Linux/macOS delivery. Windows ARM64 remains a separate future artifact and acceptance target.

Acceptance evidence records exact OS/kernel build, CPU architecture, Python ABI, artifact digest, capabilities and VM/emulation configuration. VM status must not cause rejection or weakened isolation. Rollback withdraws only the Windows artifact. No automatic merge or publication.

References (checked 2026-10-05 Europe/Berlin): GitHub runner reference, UTM architecture settings, Microsoft x86/x64 emulation.

Activity

  1. self-assigned this
    on Oct 5, 2026
  2. added
    codebaseSpecfact codebase related topic
    architectureArchitecture-related topic
    on Oct 5, 2026
  3. djm81 commented on Oct 16, 2026

    @djm81
    ContributorAuthor

    The owner approved the trusted-local Code Review hard cut on 2026-10-16, Europe/Berlin. The replacement architecture and planned scenarios are published in #513, followed by modules #514, #515, core nold-ai/specfact-cli#769, and modules #516.

    This retires the remaining capsule-only delivery scope as superseded, not completed. Historical delivered fixes, signed artifacts, branches, original tests and review records remain available. Customer-observable correctness cases are retained in replacement acceptance. Runtime implementation and installed acceptance have not occurred. No merge or release is performed.

    Closing as Not Planned under the approved replacement plan. Independent module signing/security work, including #511, is preserved.

  4. moved this from Done to Rejected in SpecFact CLIon Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

architectureArchitecture-related topicchange-proposalProposal for a new changecodebaseSpecfact codebase related topicenhancementNew feature or requestopenspecopenspec change

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions