Skip to content

Engineering stabilization sprint plan: make cnb ready for owner-led development #134

Description

@ApolloZhangOnGithub

Goal

Make cnb ready for owner-led development after the user migrates to another iMac, without spawning additional classmates before that migration. This sprint is about stabilization and operating discipline, not new large features.

Sprint window

2026-05-10 through 2026-05-24.

Operating rules

  • Do not start additional cnb classmates until the user finishes iMac migration.
  • Prefer GitHub issue/milestone/label work over editing the already-dirty local worktree.
  • Keep PRs small and independently verifiable.
  • Every implementation issue needs an explicit acceptance command or external verification step.
  • Phase 3 and experiment issues stay out of the sprint unless they unblock stabilization.

P0: unblock reliable install, ownership, CI, and release

P1: make owner-led work executable

P2: useful but not allowed to block stabilization

Tracked with priority:p2, generally after this sprint: #127, #131, #99, #56, #43, #63, #41, #42, #47, #65.

Acceptance for this planning issue

  • P0/P1 issues are labeled and placed in the sprint milestone.
  • P2 issues are labeled but not treated as blockers.
  • The next project lead/code health owner can start from this issue without rereading all open issues.
  • The user can migrate first; no new classmates are required to preserve this plan.

Metadata

Metadata

Assignees

No one assigned

    Labels

    infra基础设施/工程化org-design组织设计/团队管理phase:1Phase 1: 基础稳固priority:p0Must fix before reliable development/release

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions