# BookingFlow scoped closeout

**Date:** 2026-10-15. **Outcome:** Planned core practice sequence complete; broader application correctness not established.

## Verified record

- **10 completed manual executions:** 9 Pass and 1 Fail across 1.0 and 1.1.
- **9 distinct case designs:** 1 supplied baseline and **8 learner-authored designs developed with review**, all executed. The matching defect retest reuses BF-TC-002.
- **25 learner screenshots** supporting all 10 runs. Multi-checkpoint sequences count as one run each.
- **1 learner-discovered defect**, BF-BUG-001, with a passing exact customer-viewing retest on 1.1 and an authorized staff-view comparison. The original failure remains preserved. No other discovered or fixed defect is claimed.

The executed sequence covers a valid baseline, customer/staff viewing, Studio A upper capacity, overlap/adjacency, cancellation/history and interval reuse, valid/rejected rescheduling, staff block save/remove with customer effects, and account isolation/persistence. See [manual summary](MANUAL-TEST-SUMMARY.md) and [execution log](../execution-log.csv).

## Final saved fixture

On 1.1, Sam owns BF-001. Alex owns BF-002 through BF-006: BF-004 is Cancelled, the other four are Confirmed. BF-005 retains its rescheduled Studio A time of 14:00–15:00; BF-006 is Studio A 09:00–10:00. All are on November 17, 2026. Morgan sees all six records. BL-001 remains; the exercised BL-002 was removed. The final account is Alex after return/refresh. No reset or further mutation is required for closeout; saved evidence is already preserved.

## Evidence and environment limits

Windows desktop is known. Chrome was reported at the start; exact versions and the browser used for later runs were not independently confirmed. No deliberate cross-browser/device test was executed. Refresh and account switching are supported by learner reports and corresponding visible states; screenshots do not prove every intermediate click. Sign-out login views, password entry, and confirmation dialogs were generally not separately pictured. No browser export/local-storage inspection was supplied.

Public room schedules intentionally show occupied intervals without customer identities. Own-only booking-list findings do not mean other customers' occupancy is invisible everywhere. The application models local roles, with no server or real security boundary.

## Remaining coverage

Do not claim full coverage of title validation, invalid sign-in, lower capacity and number formats, Studio B boundaries, closed/out-of-week dates, start/duration/closing limits, partial overlaps, all roles/actions, staff cancelling others, invalid/overlapping blocks, dialog dismissal, Cancel editing, exports, storage failures, complete release isolation, browser restarts, accessibility, mobile layouts, or performance. The broader initial-build scheduling/cancellation behavior was not manually investigated; app-author checks do not substitute for it or count as findings.

## Contributions and recommendation

The learner proposed eight plans from supplied goals, executed manual interactions, supplied verdicts/screenshots, and observed the role-viewing failure. Mentor review corrected some credentials, test fixtures, expectations, and workflow details and added evidence/persistence checkpoints. Prioritization and the High triage suggestion were mentor-supplied; independent learner risk prioritization was not demonstrated. The assistant supplied the app, requirements, baseline, goal prompts, seeded builds, implementation, and formatted records. App-author checks remain separate from these 10 executions.

Close the learning assignment with these limits. The recorded viewing defect is verified for its matching 1.1 fixture; a release-wide quality or business acceptance decision would require additional coverage. This is independent guided practice, not employment, client work, a user-research study, or production sign-off. No learner coding, scripts, APIs, SQL, automation, or measured business outcome is claimed. The package remains local and unpublished.