Files
AndreaSlopFotografie/aidlc-docs/features/frontend-shell/aidlc-state.md
T
SluijsensandClaude Opus 5.5 e6436601a4
Continuous Integration / check (pull_request) Failing after 6m55s
Continuous Integration / lighthouse (pull_request) Skipped
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / deploy-production (pull_request) Skipped
Adds Gitea Actions CI/CD for test and production
The pipeline runs lint, format, tests, build, dependency audit and
Lighthouse (mobile and desktop, Playwright Chromium on the arm64 runner)
on every pull request, push to master and manual run.

Pushes to master deploy to test automatically, and any branch can be
deployed to test manually. Test is a Raspberry Pi with nginx next to the
current WordPress site; the deploy refuses folders containing WordPress.
Production deploys are manual and only from release/* branches, over
FTP with TLS to the IIS webhost.

The IIS web.config and both nginx configs are generated from the same
security header list as the Vite servers, with a test that fails when
the generated files drift. Adds .gitattributes for LF line endings and
pins pnpm through packageManager.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 00:18:51 +02:00

3.2 KiB

AI-DLC State Tracking

Project Information

  • Feature Name: Front-end application shell (header/navigation, footer, shell chrome)
  • Feature Slug: frontend-shell
  • Project Type: Brownfield
  • Start Date: 2026-10-14T09:46:02Z
  • Current Stage: OPERATIONS - Deployment Setup (awaiting approval)
  • Branch: feature/frontend-shell

Workspace State

  • Existing Code: Yes
  • Programming Languages: TypeScript (React/TSX)
  • Build System: pnpm + Vite (tsc && vite build)
  • Project Structure: Single front-end SPA in web/; static HTML design reference in design/andreaslop-static/; .NET back-end planned but not present
  • Reverse Engineering Needed: Yes
  • Workspace Root: C:\Users\bdslo\Documents\Development\AndreaSlopFotografie

Code Location Rules

  • Application Code: Workspace root (NEVER in aidlc-docs/) — front-end lives in web/
  • Feature Documentation: aidlc-docs/features/frontend-shell/ only
  • Shared Artifacts: aidlc-docs/_shared/
  • Structure patterns: See code-generation.md Critical Rules

Language Configuration

  • Documentation Language: English
  • Conversation Language: User Language (Dutch)

Extension Configuration

Extension Enabled Decided At
Security Baseline Yes Requirements Analysis
Property-Based Testing Yes (full enforcement) Requirements Analysis

Operations Configuration

  • Include Operations Phase: Yes
  • Decided At: Build and Test

Deployment Setup

  • Included: Yes
  • Method: CI/CD (Gitea Actions) — test via SSH/scp to Raspberry Pi nginx, production via FTPS to IIS webhost (manual, release/* only)

Scope Notes (from user)

  • Side area / "Info menu" from the static design is OUT of scope (deliberately left out)
  • E-mail address in the mobile menu is OUT of scope (deliberately left out)

Execution Plan Summary

  • Total Stages: 13 (excluding Operations)
  • Stages to Execute: Application Design, Functional Design, NFR Requirements, Code Generation, Build and Test
  • Stages to Skip: User Stories (single persona, concrete FRs), Units Generation (single unit), NFR Design (small patterns, folded into NFR Requirements + code plan), Infrastructure Design (no infrastructure)

Stage Progress

🔵 INCEPTION PHASE

  • Workspace Detection
  • Reverse Engineering
  • Requirements Analysis
  • User Stories - SKIP
  • Workflow Planning
  • Application Design - EXECUTE (approved)
  • Units Generation - SKIP

🟢 CONSTRUCTION PHASE

  • Functional Design - EXECUTE (approved)
  • NFR Requirements - EXECUTE (approved)
  • NFR Design - SKIP
  • Infrastructure Design - SKIP
  • Code Generation - EXECUTE (approved)
  • Build and Test - EXECUTE (complete)

🟡 OPERATIONS PHASE

  • [~] Deployment Setup - EXECUTE (artifacts generated, awaiting approval)
  • Monitoring Setup - EXECUTE
  • Production Readiness Validation - EXECUTE

Current Status

  • Lifecycle Phase: OPERATIONS
  • Current Stage: Deployment Setup
  • Next Stage: Monitoring Setup

Reverse Engineering Status

  • Reverse Engineering - Artifacts generated on 2026-10-14T09:58:04Z (approved 2026-10-14T10:05:21Z)
  • Artifacts Location: aidlc-docs/_shared/reverse-engineering/