Skip to content

Plan integration 8: Reconcile release contract and verify #15

Closed

Description

@NetDevAutomate

Parent

What to build

Make public claims, installer behavior, capability specs, and full-system evidence match the completed plan-aware Now, MCP lifecycle, and Web architect product.

Acceptance criteria

  • Study Plans, Now, Today, Web, MCP, and installer language describe the implemented automatic boundaries accurately.
  • Active-learning, MCP, Web UI, agent-adapter, and CLI capability specs are synchronized.
  • CLI, Web, MCP, and architect journeys document both supported behavior and remaining live-session-binding exclusions.
  • Every acceptance area in parent issue Integrate Study Plans across Now, Web architect, and MCP #7 maps to completed child tickets and verification evidence.

Blocked by

Definition of Done

  • The full unit suite passes.
  • Representative Web and MCP integration journeys pass independently and in the combined run.
  • The combined integration run has no nested-event-loop ordering regression.
  • All public documentation, installer output, and capability matrices agree.
  • Repository status is clean and no temporary artifacts remain.
  • Parent issue Integrate Study Plans across Now, Web architect, and MCP #7 has no unverified in-scope requirement.

Activity

  1. added
    ready-for-agentImplementation-ready specification with settled requirements and test seams
    on Sep 4, 2026
  2. added 20 commits that reference this issue on Sep 17, 2026
  3. NetDevAutomate commented on Sep 18, 2026

    @NetDevAutomate
    OwnerAuthor

    Status: three of four criteria met; the fourth is mapped and closes with its last child. Source: docs/architecture/plan-integration/receipts/issue-closeout-draft-2026-09-16.md, re-verified against main at a5b9f903 (2026-09-18). Legend as on #8.

    Acceptance criterion Met Evidence
    Study Plans, Now, Today, Web, MCP, and installer language describe the implemented automatic boundaries accurately yes docs/study-plans.md ("Plan-aware now" with eligibility and the rubric's state; "Deliberately not automatic" — bold lead phrases == studyloop.planning.boundaries.NOT_AUTOMATIC, six automations, the door facts in prose; "Recording, retries, and deletion"; since 2026-09-18 the consensual close beside the list), docs/agent-install.md, agents/mcp/README.md (32 tools == registry), README.md, docs/index.md, docs/web-ui-guide.md, docs/cli-reference.md, docs/roadmap.md; the installer prints the nine lifecycle tools + record_plan_learning, per-harness reach and the whole boundary from the same constants; the architect persona's fallback table matches; all pinned by T: test_docs_plan_integration_contract.py (25) and T: test_plan_architect_persona.py (21). mkdocs build --strict clean on main
    Active-learning, MCP, Web UI, agent-adapter, and CLI capability specs are synchronized yes promoted from the change's delta specs by openspec archive plan-application-seam; the follow-on deltas (openspec/changes/plan-integration-followons/specs/) carry items 1–4's requirements; openspec validate --specs --all: 25 passed on main
    CLI, Web, MCP, and architect journeys document both supported behavior and remaining live-session-binding exclusions yes "Deliberately not automatic" (six exclusions incl. no scheduled recurring planning sessions; same single session slot); docs/acceptance-testing.md scope note; the Archify spec's rose card (C: dcfd44e4)
    Every acceptance area in parent issue #7 maps to completed child tickets and verification evidence mapped; one child open the parent mapping is posted on #7. Children #8, #9, #11, #12, #13, #14 are closed on their evidence; #10 stays open on rubric row 3b (follow-on item 5, D-F)

    DoD. Both package suites pass independently — R: receipts/verify-d0251fd1.json: full-suite-agent-session-tools 2146 passed; full-suite-studyloop is red in the sandbox on exactly the 44 environmental ids named on the receipt (R: receipts/full-suite-control-item4-2026-09-18.md), and green in CI on main (run 35374196645, 15/15 jobs incl. the 3.12/3.13 matrix, e2e 568 and install-smoke). Web and MCP journeys independently (combined-journey 3, browser-journey-e2e 11) and combined in one process in both file orders (integration-combined, integration-combined-reverse) with no nested-event-loop regression; docs, installer output and capability matrices agree (docs contract).

    Open: this issue closes with #10.

  4. added this to the 0.5.0 milestone on Sep 20, 2026
  5. NetDevAutomate commented on Sep 21, 2026

    @NetDevAutomate
    OwnerAuthor

    Closed: completed. The 2026-09-18 status comment left one criterion open — "every acceptance area in parent issue #7 maps to completed child tickets and verification evidence; one child open" — and named the finish: "this issue closes with #10." #10 closed today on item 5 (D-F) landing and rubric row 3b being scored; every child of #7 is now closed on its evidence.

    Release contract on main at 96806feb (owner pushed main 2026-09-21, PR #28 merged as a fast-forward):

    • Docs, installer output and capability specs still agree after item 5: T: packages/studyloop/tests/test_docs_plan_integration_contract.py pins the prose; design §5 (decisions 9 and 10) and the follow-on spec deltas were amended with the item-5 fixes in the same commits that changed behaviour (C: fb63fb6b, C: 291e8691).
    • DoD "full unit suite passes": CI on PR feat(now): item 5 (D-F) — energy demand for repair and the body-doubling floor #28's head 96806feb was 15/15 (3.12/3.13 matrix, e2e, install-smoke, browser-smoke, js). CI on main at the same sha is running as this closes — 13 jobs green, test (3.12), test (3.13) and e2e still in progress on an identical tree.
    • DoD "no nested-event-loop ordering regression": unchanged since 2026-09-18 (integration-combined and integration-combined-reverse in R: receipts/verify-d0251fd1.json); nothing in items 5's diff touches the journey runners.
    • DoD "parent has no unverified in-scope requirement": Integrate Study Plans across Now, Web architect, and MCP #7's closing comment states the three items that remain unverified by owner decision (its 1, 4 and 7) plainly, so the record is honest rather than clean by omission.
    • DoD "repository status is clean": the tracked tree is clean at 96806feb. The owner's working copy carries an in-progress study-notes skill and a scratch CI log that are not part of this programme; noted, not touched.

    Ships in 0.5.0 (PR #29).

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

    ready-for-agentImplementation-ready specification with settled requirements and test seams

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions