worktree start does not link gitignored runtime files (.venv, .sdlc/project.yaml)

jared commented

2026-10-10 13:40:44 +00:00

Owner

Problem

The worktree start command does not link gitignored runtime files into a new worktree. A worktree for a project that depends on these files cannot run its test suite. The programmer repair rounds cannot fix this, because the defect is in the environment and not in the code.

Observed

worktree start ticket-13 in /home/jared/projects/finance printed:

linked: .cc-os, .sdlc/pipeline.db

It did not link .sdlc/project.yaml or the gitignored .venv/ directory.

The finance test suite calls .venv/bin/bean-query. In the worktree, 4 tests failed with:

Errno::ENOENT: No such file or directory - .../worktrees/ticket-13/.venv/bin/bean-query

The os-sdlc suite-check gate failed 3 times. The run escalated with bound_exhausted:suite-check/fail (implementation 1, ticket forgejo:jared/finance#13).

The orchestrator fixed the defect by hand. It ran ln -s /home/jared/projects/finance/.venv .venv and copied .sdlc/project.yaml into the worktree.

Reproduce

worktree start ticket-13
.venv/bin/bean-query --version

Run the second command inside the new worktree. It fails with No such file or directory because .venv is not linked.

Approach

Suggested direction only. This is not a decision.

Let a project declare extra paths to link, for example a key in .cc-os/config.
Or link .sdlc/project.yaml by default.
And/or have suite-check classify ENOENT on a gitignored path as an environment defect, not a code failure.

Origin

Trigger: worktree start ticket-13 in /home/jared/projects/finance, followed by the suite-check gate run for forgejo:jared/finance#13.
Improvised this session: ln -s /home/jared/projects/finance/.venv .venv and a manual copy of .sdlc/project.yaml.
Chain: suite-check fails with ENOENT on .venv/bin/bean-query ← worktree start does not link gitignored runtime files. Stop end: IMPROVISATION (the manual symlink and copy above).
Root candidate: this ticket.
Where: worktree CLI (os plugin) start linking.
Session: c3082dee-a586-4348-8b60-57e64b92833a
Transcript: /home/jared/.claude/projects/-home-jared-projects-finance/c3082dee-a586-4348-8b60-57e64b92833a.jsonl

Discoverer: /home/jared/projects/finance, session c3082dee-a586-4348-8b60-57e64b92833a, 2026-10-10. The worktree start linking step omits gitignored runtime files that the test suite needs.

## Problem The `worktree start` command does not link gitignored runtime files into a new worktree. A worktree for a project that depends on these files cannot run its test suite. The programmer repair rounds cannot fix this, because the defect is in the environment and not in the code. ## Observed `worktree start ticket-13` in `/home/jared/projects/finance` printed: ``` linked: .cc-os, .sdlc/pipeline.db ``` It did not link `.sdlc/project.yaml` or the gitignored `.venv/` directory. The finance test suite calls `.venv/bin/bean-query`. In the worktree, 4 tests failed with: ``` Errno::ENOENT: No such file or directory - .../worktrees/ticket-13/.venv/bin/bean-query ``` The os-sdlc suite-check gate failed 3 times. The run escalated with `bound_exhausted:suite-check/fail` (implementation 1, ticket forgejo:jared/finance#13). The orchestrator fixed the defect by hand. It ran `ln -s /home/jared/projects/finance/.venv .venv` and copied `.sdlc/project.yaml` into the worktree. ## Reproduce ``` worktree start ticket-13 .venv/bin/bean-query --version ``` Run the second command inside the new worktree. It fails with `No such file or directory` because `.venv` is not linked. ## Approach Suggested direction only. This is not a decision. - Let a project declare extra paths to link, for example a key in `.cc-os/config`. - Or link `.sdlc/project.yaml` by default. - And/or have suite-check classify `ENOENT` on a gitignored path as an environment defect, not a code failure. ## Origin - Trigger: `worktree start ticket-13` in `/home/jared/projects/finance`, followed by the suite-check gate run for forgejo:jared/finance#13. - Improvised this session: `ln -s /home/jared/projects/finance/.venv .venv` and a manual copy of `.sdlc/project.yaml`. - Chain: suite-check fails with `ENOENT` on `.venv/bin/bean-query` ← `worktree start` does not link gitignored runtime files. Stop end: `IMPROVISATION` (the manual symlink and copy above). - Root candidate: this ticket. - Where: `worktree` CLI (os plugin) start linking. - Session: c3082dee-a586-4348-8b60-57e64b92833a - Transcript: /home/jared/.claude/projects/-home-jared-projects-finance/c3082dee-a586-4348-8b60-57e64b92833a.jsonl -------- **Discoverer:** /home/jared/projects/finance, session c3082dee-a586-4348-8b60-57e64b92833a, 2026-10-10. The worktree start linking step omits gitignored runtime files that the test suite needs.

jared added the

plugin/os

filed-by/agent

labels

2026-10-10 13:40:44 +00:00

jared referenced this issue

2026-10-10 13:55:27 +00:00

Require exactly one category per ticket at capture and refuse non-code-change in implement #973

jared added the

category/code-change

label

2026-10-10 13:55:57 +00:00

jared referenced this issue from a commit

2026-10-12 14:02:16 +00:00

docs(takedown): ADR-0289 relevance step and #995 build records; research-only runs on #992 #984 #982

jared referenced this issue

2026-10-18 18:58:42 +00:00

worktree start links .sdlc/pipeline.db but not .sdlc/project.yaml, so os-sdlc-runner cannot open in the worktree #526

jared commented

2026-10-18 19:15:06 +00:00

Author

Owner

Evidence folded in from #526 (older, closed as superseded): hyperthrive-websites, session 01WczDUXXTYSuFuZNRQQLf49, 2026-09-03. After 'worktree start ticket-19' the worktree had .sdlc/pipeline.db linked but not .sdlc/project.yaml (gitignored in main), so os-sdlc-runner could not open the project; the user copied the file by hand. #526 expected one of two fixes: start links or copies project.yaml, or os-sdlc-runner resolves project.yaml from the main checkout. The second option is not in this ticket's Approach. Acceptance criteria #526 had: none beyond the expected behavior. Add one here: given a gitignored .sdlc/project.yaml in the main checkout, os-sdlc-runner opens in a new worktree.

jared referenced this issue

2026-10-18 19:15:06 +00:00

worktree start links .sdlc/pipeline.db but not .sdlc/project.yaml, so os-sdlc-runner cannot open in the worktree #526

jared referenced this issue

2026-11-06 16:51:44 +00:00

Move os:worktree and handoff git calls into os-git Worktree and Integration #1589

jared referenced this issue

2026-11-06 16:54:49 +00:00

Build os-git end to end (orchestrator) #1610

jared commented

2026-11-06 19:49:09 +00:00

Author

Owner

From #1589 port check: FIXED for the config route, but not by the port; it is not related to the port. Links reads worktree-symlinks from .cc-os/config and links each entry that exists in the main checkout (plugins/os-git/lib/os_git/worktree/links.rb:72,127-134), so .venv and .sdlc/project.yaml link when listed. The port keeps this. There is no default link for them, and the suite-check ENOENT classification idea is not in this code. Not closed.

Rows
Columns

worktree start does not link gitignored runtime files (.venv, .sdlc/project.yaml) #982

Problem

Observed

Reproduce

Approach

Origin