Answer: - delay implementation of public - too big of a change for now; keep folder
but add task to do this in a later phase

Open item — not yet resolved by the tree alone

.env - exists off websites/apps/appname/.env - for each app it overrides
Answer: websites/system/.env - again it will be customized for app definitions; api
keys,login required, database access specific to app, appname etc

Pilot: what changes in `defapp` to test this

`defapp` currently has: `admin, ai/{output,prompts}, audit, config, css/themes,
data/{config,fonts,logs,sql}, docs, img, js, pages, php, scripts, sql, src/
{Controllers,Helpers,Parser}, templates, tests, tmp, tools`.

To bring it in line with v2, add:
- [ ] `public/` — Answer: keep folder - delay implementation
- [ ] `var/sessions/` — if defapp handles its own sessions rather than a shared
mechanism; Answer: this probably should be handled at the system level - so the
session goes across apps?
- [ ] `docs/adr/` and `docs/runbooks/` — currently `docs/` is flat
Answer: remove runbooks - not required; add adr to glossary; docs has multiple
masters - project managemen, ai, and viewing by grouping; need a rule
perhaps keep flat and create json file to group md files for viewing as
groups in ux; json - group, purpose, short.name, filename, date.created,
date.updated, comment etc
- [ ] `config/templates/` — currently `config/` is flat; Answer: keep flat; need to
- keep config flat (store all json files here)
- [ ] sql - Answer: stay top level;
- Answer: data - should be for temporary information and permanent ? data/fonts
data/tmp/sessions data/tmp/logs
- [ ] Decide whether `src/` (OOP) or `php/` (procedural) is defapp's actual
- Answer src OOP; php js procedural ; rule stay procedural unless OOP is better
alternative for native use PDO,
src/Database Diagnostics Logging Models Controllers Helpers Parser

Nothing here needs `api/`, `python/`, or `assets/` — defapp has no declared
extensions, which is correct for a default/reference app.
- Answer: why wouldn't we create these in default scaffolding so apps know where to add
them?
- we need a appname.manifest file to determine what files should be in app? Good
or bad idea