first commit

This commit is contained in:
2026-05-29 14:48:36 +08:00
parent 708d2c0d04
commit 0cc2c6bdf7
66471 changed files with 2561203 additions and 6 deletions

View File

@@ -0,0 +1,86 @@
---
phase: quick
plan: 1
type: execute
wave: 1
depends_on: []
files_modified:
- src/templates/dashboard.html
- src/templates/settings.html
- src/templates/calibration.html
- src/templates/files.html
autonomous: true
requirements: []
user_setup: []
---
<objective>
Add TCK logo to the navigation bar in all 4 app templates.
</objective>
<context>
Logo files available in project:
- logo/[LOGO] TCK.svg (primary)
- logo/[LOGO] TCK_small.png (fallback)
All 4 templates share a common navigation structure:
```html
<nav class="nav-menu">
<a href="/" class="nav-btn">...</a>
<a href="/settings" class="nav-btn">...</a>
...
</nav>
```
</context>
<tasks>
<task type="auto">
<name>Add logo to all 4 template navigation bars</name>
<files>src/templates/dashboard.html, src/templates/settings.html, src/templates/calibration.html, src/templates/files.html</files>
<action>
Add the TCK logo image to the START of the navigation bar in each template. Use the SVG logo at path "logo/[LOGO] TCK.svg".
For each template, add this as the first element inside the `<nav class="nav-menu">`:
```html
<a href="/" class="nav-logo">
<img src="logo/[LOGO] TCK.svg" alt="TCK" height="40">
</a>
```
Also add CSS for the logo in each template's `<style>` section (add after .nav-btn styles):
```css
.nav-logo {
display: flex;
align-items: center;
justify-content: center;
padding: 0 10px;
}
.nav-logo img {
max-height: 40px;
width: auto;
}
```
Apply to: dashboard.html (lines 262-276), settings.html (lines 167-181), calibration.html (lines 201-215), files.html (lines 218-232)
</action>
<verify>
<automated>grep -l "nav-logo" src/templates/*.html | wc -l</automated>
</verify>
<done>Logo appears in navigation bar of all 4 templates</done>
</task>
</tasks>
<verification>
- [ ] Logo image tag present in all 4 template navigation bars
- [ ] Logo CSS styling added to all 4 templates
</verification>
<success_criteria>
All 4 templates display TCK logo in their navigation bar
</success_criteria>
<output>
After completion, create .planning/quick/1-add-a-logo-to-the-app-logo-can-be-found-/1-SUMMARY.md
</output>

View File

@@ -0,0 +1,64 @@
---
phase: quick
plan: 1
subsystem: ui
tags: [logo, navigation, bootstrap]
requires: []
provides:
- TCK logo added to all 4 template navigation bars
affects: []
tech-stack:
added: []
patterns:
- Logo navigation placement (leftmost in nav-menu)
key-files:
modified:
- src/templates/dashboard.html - Added logo to navigation
- src/templates/settings.html - Added logo to navigation
- src/templates/calibration.html - Added logo to navigation
- src/templates/files.html - Added logo to navigation
key-decisions: []
requirements-completed: []
---
# Quick Task 1: Add Logo to App Navigation
**Added TCK logo to navigation bar in all 4 Flask templates**
## Performance
- **Tasks:** 1
- **Files modified:** 4
## Accomplishments
- Added .nav-logo CSS styling to all 4 templates
- Added logo image at start of each navigation bar
- Logo uses logo/[LOGO] TCK.svg at 40px height
## Commits
- `d18ef95` - feat(quick-1): add TCK logo to all 4 template navigation bars
## Files Modified
- `src/templates/dashboard.html` - Added logo to navigation bar
- `src/templates/settings.html` - Added logo to navigation bar
- `src/templates/calibration.html` - Added logo to navigation bar
- `src/templates/files.html` - Added logo to navigation bar
## Verification
- grep confirms nav-logo in all 4 templates (12 matches: 3 CSS + 1 HTML per file)
- Logo image tag verified in all 4 templates
## Deviations from Plan
None - plan executed exactly as written.
## Issues Encountered
None
---
*Phase: quick-1*
*Completed: 2026-03-12*

View File

@@ -0,0 +1,124 @@
---
phase: quick
plan: 2
type: execute
wave: 1
depends_on: []
files_modified: []
autonomous: true
requirements: []
user_setup: []
must_haves:
truths:
- "Current Flask v1 interface is preserved in a dedicated directory"
- "v2 project structure is initialized with sample_interface as reference"
artifacts:
- path: "src_v1/"
provides: "Archived Flask application (app.py + templates)"
- path: "v2/"
provides: "New v2 project based on sample_interface"
key_links: []
---
<objective>
Store the current Flask v1 interface and initialize v2 project based on sample_interface reference implementation.
Purpose: Preserve working v1 while setting up v2 development environment using the React/Next.js sample as a template.
Output:
- src_v1/ - Archived Flask v1 application
- v2/ - Initial v2 project structure (copied from sample_interface)
</objective>
<context>
@./.planning/STATE.md
# v1 Interface (current - to be archived)
src/app.py - Flask backend
src/templates/dashboard.html - Main rainfall dashboard
src/templates/calibration.html - Sensor calibration page
src/templates/files.html - Flash memory/file manager
src/templates/settings.html - System settings
# v2 Reference (sample_interface)
sample_interface/guidelines/Guidelines.md - Design system specification
sample_interface/src/app/ - Complete React app structure
</context>
<tasks>
<task type="auto">
<name>task 1: Archive current Flask v1 interface</name>
<files>src_v1/app.py, src_v1/templates/*.html</files>
<action>
1. Create src_v1/ directory
2. Copy src/app.py to src_v1/app.py
3. Copy src/templates/*.html to src_v1/templates/ (create directory first)
4. Copy src/static/ to src_v1/static/ (if exists)
5. Copy src/data/ to src_v1/data/ (if exists)
6. Copy src/routes/ to src_v1/routes/ (if exists)
7. Copy src/services/ to src_v1/services/ (if exists)
8. Copy requirements.txt to src_v1/requirements.txt
This preserves the complete working Flask v1 application.
</action>
<verify>
<automated>ls -la src_v1/ && ls src_v1/templates/</automated>
</verify>
<done>src_v1/ directory exists with complete Flask application copied</done>
</task>
<task type="auto">
<name>task 2: Initialize v2 project from sample_interface</name>
<files>v2/</files>
<action>
1. Create v2/ directory
2. Copy entire sample_interface/src/ to v2/src/
3. Copy sample_interface/package.json to v2/ (create if needed)
4. Copy sample_interface/tsconfig.json to v2/ (if exists)
5. Copy sample_interface/vite.config.ts to v2/ (if exists)
6. Copy sample_interface/index.html to v2/ (if exists)
7. Copy sample_interface/guidelines/ to v2/guidelines/
This establishes v2 project with the sample React interface as starting point.
</action>
<verify>
<automated>ls -la v2/ && ls v2/src/app/</automated>
</verify>
<done>v2/ directory exists with React application structure from sample_interface</done>
</task>
<task type="auto">
<name>task 3: Document v1 and v2 structure in README</name>
<files>README.md</files>
<action>
Update project README to document the new v1/v2 structure:
- Explain src_v1 contains the archived Flask v1 application
- Explain v2 contains the new React-based interface
- Reference which interface is currently active/deployed
Add a version history section documenting this transition.
</action>
<verify>
<automated>grep -E "v1|v2|version" README.md</automated>
</verify>
<done>README documents the v1/v2 structure and version history</done>
</task>
</tasks>
<verification>
- [ ] src_v1/ contains complete Flask application
- [ ] v2/ contains React application from sample_interface
- [ ] README documents the new structure
</verification>
<success_criteria>
- Current Flask v1 interface archived in src_v1/
- v2 project initialized with sample_interface React code
- Project documentation updated
</success_criteria>
<output>
After completion, create `.planning/quick/2-store-this-current-interface-as-v1-and-w/2-SUMMARY.md`
</output>