# Team Duckies Flat-File Core v0.0.8 handoff

## Product direction

Team Duckies is a privacy-minimal, database-free motorsports team site. Public delivery is generated HTML. Administrators and Discord-owned players edit ordinary JSON and CSV files through forms.

The approved public identity remains the v0.0.5 black/gold/red design with the crest-left, TEAM DUCKIES-center, race-car-right homepage hero. Future functional work must preserve that composition unless the team explicitly changes direction.

## Current platform

- Email one-time-code Admin login
- Automatic root/subfolder URL detection
- JSON members, setups, and events
- CSV Auto Legends vehicle catalog
- File locks, atomic writes, history copies, and content ZIP backups
- Static page publisher and sitemap/search-index generation
- Event Randomizer
- Discord OAuth/player ownership scaffold
- Discord interaction endpoint

## v0.0.8 Auto Legends setup system

- Game-aware setup records with `game_id` and schema version
- Automatic stable slugs
- Automatic stable `AL-#########` share codes
- Auto Legends 1/4 Mile and 1/2 Mile categories
- 32 supplied cars in `content/games/auto-legends/cars.csv`
- Admin car catalog editor with active/inactive status
- Managed vehicle selector plus manual fallback
- HP, torque, weight, and performance notes
- One through ten forward gears with add/remove controls
- Front/rear ride height, camber, spacer, rim diameter, rim width, and tire stretch
- Structured performance-part groups with stock/installed state, allowed rarity, exact part name, and notes
- Tire-specific choices
- Updated public build sheets, Garage cards, filters, player submission, and Discord output

## Data ownership

No SQL database is used. Content backups include the entire `content/` directory, including game configuration and the car CSV. Temporary authentication, sessions, logs, rate-limit files, and credentials remain outside those backups.

## Important implementation rules

- Do not make slugs or share codes user-editable.
- Keep existing slugs and codes stable when a setup title changes.
- Deactivate catalog cars instead of removing cars referenced by setups.
- Do not invent missing HP, torque, weight, rim limits, or part data.
- Treat share codes as convenient lookup identifiers; private authorization still depends on Admin or Discord identity.
- Keep game-specific rules in `content/games/GAME-ID/` so future games can use different categories and setup fields.

## Next feedback targets

1. Real-world testing of the Auto Legends setup form
2. Per-car default gear counts and rim limits
3. Exact loot-crate part naming, upgrade levels, and randomized-stat fields
4. Public build-sheet density and mobile readability
5. Car-catalog import/export workflow
6. Discord player submission once credentials are active
7. Adding a second game profile to validate the multi-game architecture

## Deployment dependency

Production email codes require working PHP mail or authenticated SMTP. Discord functionality requires application credentials. Neither dependency changes the flat-file content model.