Skip to content

Offer a working retry after descriptor-based interface closure #279

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Part of #120. This delivery does not retire an adoption or release gate.

Evidence and audience

Host-enforced closure always directs users to the manifest action. Descriptor users have an empty required manifest, so that retry cannot submit their existing descriptor. This affects product authors and consumers using the documented workflow.

Intended outcome

Make the declared workflow reliable without widening source access or moving data or credentials into controller metadata. A focused failing regression is the acceptance proxy; implementation tests do not establish independent production adoption.

Acceptance criteria

  • Remember the explicit import path for a closed descriptor session.
  • Offer a working explicit descriptor retry without reconstructing a UI manifest.
  • Revalidate current inputs and grants; keep closed sessions withdrawn until that explicit action.

Rough size: S.

Activity

  1. added theissue type on Oct 5, 2026
  2. moved this to 🫴 Ready in 🌊 Project Boardon Oct 5, 2026
  3. self-assigned this
    on Oct 5, 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 #282 at source 19c7ec790522f4a6ddf819929de86ee3953a951a, with reviewed and tested head 1d5621a06e0c01e8f85d3de00627ba4e57661764.

    All 38 hosted results settled: 36 passed and two expected automation skips. CI exercised controller/API/chart checks, TLS browser interaction, real SQL/JSONB/AGE, Document and Graph queries and Kubernetes recovery lifecycle. The five deterministic cancellation-boundary regressions were RED before the repair and GREEN under 100 race iterations, while real connector timeout failures remain observable.

    The complete local build/race/browser/provider-fixture/lint and chart contract validation passed. Exact-head review is recorded as GitHub review 5409858648 after verified provider usage limits, with an independent clean review of all eight paths.

    This completes the source delivery. Production upgrade and authenticated public user-path verification remain tracked separately in devantler-tech/platform#4499; production adoption gates remain unchanged.

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