Skip to content

Port: the paths a pull request changes, with both names of a rename #138

Closed

Description

@don-petry

Part of the epic "Epic: slice 0, foundations. The repo holds the line, its context is tested, and the platform facts are recorded".

Follows "Kernel: a change to the Factory's own rules or a Lens's inputs needs a person" (#113), built by PR #135 (decision 0020): its working rulings named this as out of scope.

Why. The Kernel reads changed_paths (one {path, previous} record per changed file, exactly diff.files of them) and complete.changed_paths. Until adapters/ exists, only fixtures produce them. A rename the port reports with previous: null the Kernel cannot detect.

Done when

  • The port reads every file of the pull request (paginated in full) and sets complete.changed_paths only when it did.
  • A rename or copy gives both names; a trial fixture grounds it.
  • Waits on adapters/.

Activity

  1. don-petry commented on Oct 19, 2026

    @don-petry
    ContributorAuthor

    Moved (plan review, 2026-10-19). This waits on a reserved directory, so it is slice-1 work, not slice 0's. It is now a sub-issue of "Epic: slice 1, first approval. A Release on next reviews a pull request to this repo, and the machine user's approval stands" (#182), and its Done-when is folded into the story that creates that directory (the facts port, #191, for the port's paths; the Harness, #194, for apply's refusal). It closes with that story.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions