• (59b23b7) Stop the board walk on a link that does not resolve, and bump to 0.23.1

    Ghost released this 2026-08-23 11:47:31 +00:00 | 69 commits to master since this release

    find_worklane_dir asked exists(), which follows a symlink. A .worklane
    that was a dangling link therefore answered exactly as no .worklane at
    all: the walk carried on up the tree, the first board above the project
    became the board, and every write landed in it. Silently, and in the board
    belonging to someone else's project.

    Latent while a board is a real directory inside the project it belongs to.
    Once boards live in one shared directory and .worklane is a link into it,
    a dangling link stops being a corrupted tree and becomes an ordinary state:
    it is what you have before the boards repo is cloned, and after a board
    directory is renamed. So this is reachable on an ordinary day rather than
    only with a hand-made link.

    classify reads symlink_metadata first, so the answer is about the entry
    rather than about its target, and it is one of four: Absent, Board,
    Dangling or NotADirectory. Absent is the only one the walk carries on
    from. A .worklane that is there but unusable is this project's board and
    is reported here, not handed to whatever sits above it. Anything other than
    NotFound out of symlink_metadata is an error too, since reading a
    filesystem that could not answer as nothing-there is how the walk-past
    worked in the first place.

    The failure names the target and says the boards repo may not be cloned.
    The old message, no board found and run worklane init, was wrong twice
    over even with no board above: it describes an empty tree, and it points at
    creating a board when the cause is an unsynced machine, which is the one
    action that produces two boards with one name.

    A regular file at that path is an error as well. It is a plausible future
    pointer form and reading it as one is that change's decision to make;
    stepping over it and writing above is the answer that is wrong today.

    A link that resolves is still indistinguishable from a real directory, and
    what comes back is the link rather than its target, so
    .worklane/backlog/*.md reads the same either way and nothing downstream
    learns whether the board is local.

    Every writing command resolves the board before it writes, so the refusal
    costs nothing halfway. add is where that is pinned end to end, against an
    empty board above the project that stays empty. init is untouched: it
    does not go through this walk, it writes nothing on a dangling link today,
    and its symlink cases belong to the layout change.

    Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

    Downloads