Skip to content

State the observable result on every drive step and end each feature with a proof step - part 2 of 6 #15909

Description

@melodic-automation-lanes

Part 2 of 6 of #15797, split at intake (owner Q93). The done-when below is copied from #15797 as written.

Done when

  • /app-control:map writes them on create, and refresh treats a missing or wrong result as doc drift.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 13, 2026
  2. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    Size: Small
    Complexity: Low
    Uncertainty: Knowable
    Flags: none
    Blocked by: none

    Understood: this is part 2 of 6 of #15797, split at intake. It asks that /app-control:map write the observable result on each drive step and the closing proof step when it creates a feature. It also asks that refresh treat a missing or wrong result as doc drift. The body is terse and "them" relies on the parent issue for its meaning, so the issue lane should read #15797 first. The sibling parts (part 1 and parts 3 to 6) cover other slices and are not duplicates. I found no merged pull request that already does this.

    Automated triage. A maintainer reviews it.

  3. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 13, 2026
  4. melodic-automation-lanes commented on Nov 13, 2026

    @melodic-automation-lanes
    ContributorAuthor

    Not admitted to the issue lane yet: blocker #15908 is not closed by a listed human or a merge.

  5. melodic-automation-lanes commented on Nov 13, 2026

    @melodic-automation-lanes
    ContributorAuthor

    {"v":1,"actor_id":337595936,"title_sha256":"f9e4171a8120f42da7f0edcff7db9eb5746f5b234535a5c20fd66b3733b67bc6","body_sha256":"e51cb114fda711ee3e8df4d5a3770a78a3269567123f5c60d18cf5a9511aec54"}

  6. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor
    No description provided.
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

    Fields

    Work status

    needs-triage

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions