Skip to content

[Sprint 19] Repair Aspire startup on new machine #350

Description

@mpaulosky

Objective

Restore full build and Aspire orchestration functionality on new development machine after initial environment setup failure.

Description

Development environment on new machine is broken:

  • Aspire service failed to start
  • Build or local testing may be blocked
  • Full environment repair is needed before feature work can continue

Scope

  1. Diagnose the Aspire startup failure
  2. Verify required dependencies (.NET SDK, Docker, MongoDB/tooling)
  3. Run the authoritative repair flow from .github/prompts/build-repair.prompt.md
  4. Verify Aspire/AppHost starts cleanly
  5. Document the repair steps and fixes

Acceptance Criteria

  • Aspire AppHost starts without errors
  • Orchestrated services come up cleanly
  • dotnet build --no-restore succeeds with zero errors and zero warnings
  • All required local test suites pass
  • The repair steps and findings are documented in build-log.txt
  • Local pre-push validation is working

Related References

  • .github/prompts/build-repair.prompt.md
  • .squad/skills/build-repair/SKILL.md
  • .squad/skills/pre-push-test-gate/SKILL.md

Notes

  • This is a blocking issue for new-machine setup
  • Zero-tolerance build/test cleanliness applies
  • Docker may be required for AppHost/integration coverage

Metadata

Metadata

Assignees

No one assigned

    Labels

    go:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a membersquad:boromirAssigned to Boromir (DevOps / Infra)squad:samAssigned to Sam (Backend / .NET)

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions