Skip to content

🔧🧑‍💻 - Record the six remaining packaged setup platform and Windows symlink observations #982

Description

@efraespada

Is there an existing issue for this?

  • I have searched the existing issues.

What area does this task affect?

CI/CD

Task description

Record the six remaining packaged setup platform and Windows symlink observations. Deliver one independently reviewable result at the separate setup acceptance; not ev-07 stage.

Scope and acceptance criteria

  • Run I039-I042 on the corresponding real self-hosted vypdev Linux/Windows environment with the packaged CLI, local fixture-only repository and no model or GitHub write calls.
  • Observe X023/X026 on the specified Windows service environment: an escaping asset symlink is not served and startup rejects an out-of-root index symlink. Record actual runner/OS/CLI/source identities and preserve failures or unavailable capabilities.
  • Keep Windows services without the codex label. These are setup/web filesystem observations, not a claim that Codex agent tools work in Windows session 0.
  • Update only the six acceptance records and necessary reproducible instructions. Keep unexecuted cases open; use the existing acceptance validator and applicable docs/spec gates. No hosted runner migration, consumer template edit or Bugbot activation.

Current issues or inefficiencies

The other six open setup cases are Linux/Windows packaged launch and browser fallback (I039-I042) plus two Windows symlink boundaries (X023/X026). A skipped or queued job and successful tests on another OS do not establish these observations.

Observed baseline: unreleased develop ccefb27627cd627ccdb7d5666fd174c2ac1da07b from merged PR #951.

Expected impact

Make this one pending result independently inspectable and reproducible, with its actual passed, failed or unavailable evidence.
Completion does not authorize release, producer trust, profile qualification from partial measurements, or production activation.

Additional context or comments

Priority and dependencies

Documentation and implementation boundary

Documentation: docs/development/setup-assistant-review.mdx.
Keep Clean Architecture and current coverage/contract gates. When a later implementation changes a public contract, update its catalogued SDD, tests and docs together and validate specifications; update Graphify after code changes.
Read the effective #950 contract in the owning SDD and its current reconciliation amendments; historical pilot deadlines are not current investigation limits.

Fixed invariants and planning state

Backlog only: no in-progress, branch creation, model execution, deployment or activation requested by this planning step.
Keep BUGBOT_VERIFICATION_MODE=disabled. Evaluated PRs must have zero write attempts; retain frozen pilots and independent evaluator/oracle evidence.
Token usage is optional telemetry and cannot stop investigation or reject a supported verdict. Elapsed time and turn count do not impose research cutoffs; explicit cancellation and evidence/SHA integrity remain mandatory. Post-run latency qualification criteria remain distinct from session deadlines.

Activity

  1. moved this to Todo in vypdevon Nov 19, 2026
  2. changed the title [-]Record the six remaining packaged setup platform and Windows symlink observations[/-] [+]🔧 - Record the six remaining packaged setup platform and Windows symlink observations[/+] on Nov 19, 2026
  3. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    Hi! I’m @vypbot, the Copilot assistant for this repository.

    I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.

    Try /copilot help to see the available commands, or mention @vypbot with your question.

  4. moved this from Todo to In Progress in vypdevon Nov 19, 2026
  5. added
    branchedIndicates that a branch has been created for this issue.
    on Nov 19, 2026
  6. changed the title [-]🔧 - Record the six remaining packaged setup platform and Windows symlink observations[/-] [+]🔧🧑‍💻 - Record the six remaining packaged setup platform and Windows symlink observations[/+] on Nov 19, 2026
  7. added
    state:workingWork can proceed on the verified branch or without a branch.
    on Nov 19, 2026
  8. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    Implementation plan

    Current status: Ready to start. No action is required from maintainers before implementation.

    1. Review the acceptance contract and repository guidance
      • Read the setup acceptance records, review instructions, and applicable project rules to confirm the six case requirements and validator gates.
    2. Prepare reproducible fixture-only procedures
      • Document commands and environment identity fields for I039-I042 and Windows cases X023/X026.
      • Keep the setup services without the codex label; use no model or GitHub write calls.
    3. Run the cases on the specified self-hosted environments
      • Use the packaged CLI on the corresponding Linux and Windows environments, and observe symlink boundaries on the specified Windows service environment.
      • Record actual runner, OS, CLI, and source identities; preserve failures and unavailable capabilities, and leave unexecuted cases open.
    4. Update only the six acceptance records
      • Record observed evidence for I039-I042, X023, and X026 in the acceptance file; make only necessary reproducibility instruction changes.
      • Keep the result separate from EV-07 and avoid hosted runner migration, consumer template edits, and Bugbot activation.
    5. Validate the acceptance update
      • Run the existing acceptance validator and applicable documentation/specification gates.

    Acceptance: The six case records contain reproducible, identity-attributed observed outcomes (or remain open if unexecuted), and the existing acceptance validator and applicable documentation/specification gates pass.

    Need something else? Mention the bot with a question or use /copilot help.

  9. added
    size: LIndicates a large-sized task or issue that requires significant effort and time.
    20%Progress: 20%
    and removed on Nov 19, 2026
  10. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    Progress · 20% estimated

    Assessed head bbf3bf16 · 1/7 supported
    0 need implementation · 6 need verification or clarification

    Verification or clarification needed

    • R11 · Record the six remaining packaged setup platform and Windows symlink observations. Deliver one independently reviewable result at the separate setup acceptance; not ev-07 stage. — Record the six attributable outcomes before treating the observation packet as complete. Requirement source · Evidence at assessed head
    • R15 · - [ ] Run I039-I042 on the corresponding real self-hosted vypdev Linux/Windows environment with the packaged CLI, local fixture-only repository and no model or GitHub write calls. — Run I039–I042 on the specified self-hosted Linux and Windows desktops and record actual outcomes. Requirement source · Evidence at assessed head
    • R16 · - [ ] Observe X023/X026 on the specified Windows service environment: an escaping asset symlink is not served and startup rejects an out-of-root index symlink. Record actual runner — Record both Windows service assertions and their actual runner, OS, CLI, source, and capability results. Requirement source · Evidence at assessed head
    • R18 · - [ ] Update only the six acceptance records and necessary reproducible instructions. Keep unexecuted cases open; use the existing acceptance validator and applicable docs/spec gat — Verify the acceptance, documentation, and applicable specification gates; reported validation is not independently attested. Requirement source · Evidence at assessed head
    • R31 · Make this one pending result independently inspectable and reproducible, with its actual passed, failed or unavailable evidence. — Record attributable passed, failed, or unavailable outcomes for the six cases. Requirement source · Evidence at assessed head
    • R46 · Keep Clean Architecture and current coverage/contract gates. When a later implementation changes a public contract, update its catalogued SDD, tests and docs together and validate — Confirm the applicable coverage and contract gates after the reported hook failure; no public contract change is shown. Requirement source · Evidence at assessed head

    Issue · Linked pull request · Full assessment

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

Metadata

Metadata

Assignees

Labels

20%Progress: 20%branchedIndicates that a branch has been created for this issue.chorein-progressStart work on an admitted issue.maintenancepriority: lowNot urgent, can be addressed later.size: LIndicates a large-sized task or issue that requires significant effort and time.state:workingWork can proceed on the verified branch or without a branch.

Projects

  • Status
    In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions