# Repository Scan

## Scope

Scanned the workspace on 2026-04-27 while bootstrapping Trellis project guidelines.

## Findings

- The workspace root is `/mnt/d/document/mzh`.
- `git status --short --branch` from the workspace root fails with `fatal: not a git repository`; no git metadata is available at this level.
- The only root-level convention file discovered by the bootstrap search is `AGENTS.md`.
- `AGENTS.md` contains Trellis-managed instructions only. It does not describe backend or frontend implementation conventions.
- No app package manifests were found at the workspace root, including `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`, or common lockfiles.
- No application source files were found outside Trellis/Codex scaffolding at shallow workspace depth. The current files are Trellis workflow/config/scripts/specs/tasks and Codex agent configuration.
- At initial scan time, existing `.trellis/spec/backend/*.md` and
  `.trellis/spec/frontend/*.md` files were unpopulated scaffold templates; they
  have since been populated during this bootstrap task.

## Later Developer Decision

The source scan remains accurate as a scan of files on disk, but it no longer
means the project stack lacks a decision. The developer later provided explicit
project requirements in
`.trellis/tasks/00-bootstrap-guidelines/research/project-requirements.md`.
Future agents should combine both facts: application source code does not exist
yet, and the intended stack is JSP + Servlet + MySQL + Tomcat with a layered
B/S architecture.

## Source-Code Evidence Boundary

Because there is no backend or frontend application code in this workspace yet,
the bootstrap specs should distinguish source-code evidence from
developer-provided decisions:

- Backend and frontend conventions are not evidenced by source files yet.
- The project stack and intended architecture are established by the developer:
  B/S layered JSP + Servlet + MySQL + Tomcat development in IDEA.
- Future agents should follow the populated `.trellis/spec/` files and
  `.trellis/tasks/00-bootstrap-guidelines/research/project-requirements.md`
  for stack, module, table, and workflow decisions.
- When new backend/frontend code is introduced, agents should update the
  matching `.trellis/spec/` files with concrete examples from that code.