# Task 1 Report - AgendaMax demo access references

## Status

Complete for the source and documentation layer. Local and production SQLite data were not touched.

## Changed files

Implementation commit `6355d18a07b5bef6fd3515b80a0f768b0ae1050b` (`docs: standardize AgendaMax demo access`) changed:

- `README.md` - added an explicit `Contraseña` column with `demo1234` for all eight demo accounts; changed only Admin and Dueño to `@agendamax.demo`.
- `server/index.ts` - changed the fresh default owner email.
- `server/scripts/seed.ts` - changed fresh admin and owner emails; retained `demo1234`.
- `src/pages/LoginPage.tsx` - changed only the development default owner email.
- `admin-test.mjs`, `e2e-test.mjs`, `e2e-full.mjs`, `server/scripts/booking-e2e.mjs`, `visual-audit.mjs` - aligned active platform login fixtures and assertions.
- `docs/superpowers/plans/2026-07-26-auto-assign-specialist-booking-redesign.md` - aligned its copy-pasteable booking login example.

The current untracked Task 1 brief, design, and migration plan were not modified or staged. The completed Task 5 report was classified as historical and was not modified. No employee email domain or password was changed.

## TDD evidence

### RED

The five executable login fixtures were updated before the source constants. A read-only source assertion was then run against `server/index.ts`, `server/scripts/seed.ts`, and `src/pages/LoginPage.tsx`. It failed as expected with `AssertionError` because `owner@agendamax.demo` and `admin@agendamax.demo` were not yet present while the old source constants remained.

The focused runtime visual check was also attempted before source changes:

```text
npm run audit:visual
page.goto: net::ERR_CONNECTION_REFUSED at http://localhost:5173/
```

This did not reach the application and did not touch the database.

### GREEN

After the minimal source and README edits, the corrected read-only assertion passed:

```text
source and active login fixtures: PASS
```

The final active-reference and README credential assertion also passed:

```text
active references and README credentials: PASS
```

## Tests and outputs

- `npm run typecheck` - passed, exit code 0; `tsc -b --noEmit` reported no errors.
- `npm run build` - passed, exit code 0; Vite transformed 2463 modules and built in 5.63s.
- `npm run test:unit` - passed: 39 tests, 39 pass, 0 fail.
- `npm run audit:visual` - unavailable: no server was listening on `localhost:5173` (`ERR_CONNECTION_REFUSED`).
- `npm run lint` - unavailable: ESLint 9.39.5 could not find `eslint.config.js`, `eslint.config.mjs`, or `eslint.config.cjs`.
- `rg -n ...` - unavailable because `rg` is not installed/on PATH in this environment. The equivalent scoped repository search found no old domain in active application, README, fixture, or executable plan references.
- `git diff --cached --check` - passed before the implementation commit.

The database-mutating API suites (`test:e2e`, `test:admin`, and `test:booking`) were not run because this task explicitly forbids touching the ignored local database. They remain for the post-migration verification task.

## Self-review

- The quick-login behavior is unchanged: `LoginPage` still loads `/api/auth/demo-users`, and the existing password and account-switching logic remain intact.
- Only platform-owned Admin and Dueño domains changed to `@agendamax.demo`; all employee domains remain on their existing business domains.
- All documented demo rows explicitly show `demo1234`, including every employee row.
- No migration, abstraction, production command, local database command, `.env.local.ps1`, or `data/` file was added or changed.
- The implementation commit contains exactly the ten intended Task 1 files and excludes the supplied untracked design/plan files.
- Remaining `@agendapro.demo` matches are intentional migration/history references in the new migration plan/spec and the completed Task 5 report.

## Concerns

- Live/API and visual login verification is pending a running dev server and the later SQLite migration; those prerequisites were intentionally not started in this task.
- Lint remains unavailable until the repository ESLint 9 configuration is supplied or the project pins a compatible ESLint setup.
- The exact `rg` inventory command cannot be reproduced until ripgrep is installed/on PATH.