Skip to content

Consume & E2E-validate the vibe-coding plugin (Stack map + conversational scenarios)Β #60

Description

@devantler

πŸ€– Generated by the Daily AI Engineer

Problem. ADR-0003 (#58, Part of #49, child 4): manifest validation proves nothing about voice or guardrail quality β€” the plugin must be verified behaviourally.

Proposal. Author devantler-tech's ## Stack map section in the consuming deployment (the monorepo's AGENTS.md; rows Building block / Good for / Owning repo + a default intake repo), then run the ADR's scenario set end-to-end: (1) in-stack build of a small app purely conversationally, (2) out-of-stack request asserting the plain-language decline + suggested-issue payload on the owning repo, (3) unmapped need asserting the catch-all default-intake redirect, (4) missing/malformed Stack map asserting the fail-closed decline.

Blocked by child 3 (assemble).

Rough size. M β€” mostly validation effort; the Stack map authoring is small.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions