Skip to content

Require complete tag-pagination metadata before proposing releases #500

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

The proposal evaluator accepts a terminal tag page with a missing or wrongly typed end cursor and returns PREPARED, treating an incomplete observation as proposal clearance.

Proposed direction

Repair the owning observation or output boundary, with a regression that fails on current main before changing the implementation. Preserve the existing conservative behavior and public interface.

Acceptance criteria

  • Require both page-info keys, a boolean continuation flag and a valid cursor representation on every page.
  • Preserve legitimate terminal cursors for populated connections and explicit null for empty terminal connections.
  • Exercise missing/type-invalid keys through the actual offline proposal command and retain UNKNOWN with no write authority.

Size: S/M. Part of #101.

Activity

  1. added theissue type on Oct 4, 2026
  2. moved this to 📥 Backlog in 🌊 Project Boardon Oct 4, 2026
  3. self-assigned this
    on Oct 4, 2026
  4. added a commit that references this issue on Oct 5, 2026
  5. devantler commented on Oct 5, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Delivered by merged PR #504 at commit 1c1b7a2. Merged-main bytes match the reviewed tree; full native CI, independent exact-head review and actual release/orchestrator evaluation are recorded on the PR. Failed preparation retains public output for inspection and preserves foreign files; the documented identity observations do not grant atomic reservation or concurrent-content serialization.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Priority

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions