Establish baseline: core documentation and memory system

Adds foundational workspace documentation:
- Core identity and operating principles (SOUL.md, IDENTITY.md, AGENTS.md, USER.md)
- Memory management system specification (MEMORY.md)
- Development team context and workflow (CONTEXT.md, PROJECTS.md)
- Environment notes template (TOOLS.md)
- Heartbeat task template (HEARTBEAT.md)

Includes super-enhanced memory system:
- JavaScript memory engine implementation
- Memory initialization and test scripts
- Daily memory logs for 2026-07-03, 2026-07-04
- Project-level memory structure for site-survey-ai

Adds project templates:
- Standard Python Flask application template

Projects/site-survey-ai/memory/DECISIONS.md

@@ -0,0 +1,37 @@
+# IT Site Survey AI - Technical Decisions
+
+## July 3, 2026 - Dashboard Implementation Approach
+**Decision**: Implement a client-side dashboard that fetches data from a new API endpoint
+**Alternatives Considered**: 
+- Server-side rendered dashboard
+- Separate admin application
+- Database-based reporting interface
+**Chosen Because**: 
+- Leverages existing Flask API infrastructure
+- Provides real-time data without page refresh
+- Maintains consistency with existing application architecture
+- Quick to implement and deploy
+
+## July 3, 2026 - Data Storage Approach
+**Decision**: Continue using in-memory storage for survey responses
+**Alternatives Considered**:
+- Implement PostgreSQL database
+- Use SQLite for local storage
+- Add Redis for caching
+**Chosen Because**:
+- Maintains simplicity of current implementation
+- Avoids additional infrastructure dependencies
+- Sufficient for current use case
+- Can be enhanced later without breaking changes
+
+## July 3, 2026 - API Endpoint Design
+**Decision**: Add GET /api/surveys/responses endpoint to retrieve all responses
+**Alternatives Considered**:
+- Add pagination to endpoint
+- Implement filtering parameters
+- Create separate admin-only endpoints
+**Chosen Because**:
+- Simple implementation that meets current needs
+- Can be extended with parameters later
+- Follows REST conventions
+- Consistent with existing API patterns