NS7 slice: Create v1 E2E fixture suite #39
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
OBJECTIVE: Collect the replay/terminal/protocol/repo/LSP fixture checks into one cheap v1 smoke command.
AUTHORITY: Parent #7
NS7: V1 release hardening and rollout; PRODUCT.md; REQUIREMENTS.md (PRODUCT.md; req: governance/001-005; all v1 requirement rows as release gates).AGENT AUTHORITY:
PARENT: #7 via explicit issue link and parent checklist.
SCOPE: The smallest source/docs/tests needed to make this behavior real and verified.
BOUNDARIES: No massive slow test matrix.
ACCEPTANCE: The v1 smoke command runs in CI/local and covers open/edit/save, socket, panels, repo search/git, Tree-sitter/LSP fakes, and profile diagnostics where available.
VERIFICATION: Run the cheapest command that proves acceptance. Include regular tests for the intended payoff and adversarial tests for realistic failure, boundary, or regression cases. If no implementation test command exists yet, create/record the canonical command in AGENTS.md as part of the slice.
BLOCKERS: none
GOAL: Implement this vertical slice to the ACCEPTANCE above, keep the repo clean, cite relevant
req:anchors in code/tests where applicable, and close only after verification passes.Implemented in commit
a1600e511a(Add v1 smoke fixture target).Verification:
Regular tests: added
zig build v1-smoke, a cheap fixture suite that exercises open/edit/save UI behavior, local socket context, repo picker/search boundaries, syntax rows, LSP hover rows, and parameter movement. AGENTS.md now includes the smoke target in canonical checks.Adversarial tests: smoke rejects non-local socket paths, verifies ignored repo files stay out of picker rows, rejects invalid LSP navigation rows, and checks profile status continues to expose not-built remote/plugin boundaries.
Boundary: one deterministic smoke target only. No device/browser automation, CI matrix, screenshots, benchmarking, or new external test dependencies.