chore: moving towards agentic development
Some checks failed
Backend CI/CD / build_and_deploy (push) Has been cancelled
Frontend CI/CD / build_and_deploy (push) Has been cancelled

This commit is contained in:
2026-04-24 21:12:26 -04:00
parent df3e602015
commit b6eb692c27
179 changed files with 2880 additions and 866 deletions

View File

@@ -0,0 +1,64 @@
# Task: Align repository with bootstrap scaffold
## Feature
`docs/FEATURES/platform-scaffold.md`
## Goal
Move the current Socialize repository into the structure that `bootstrap-vdp-agentic.sh` would have generated, without replacing the existing product implementation.
## Context
The script generates a simple .NET + Vue monorepo with:
- backend under `backend/src/<App>.Api`
- tests under `backend/tests/<App>.Tests`
- root scripts under `scripts/`
- Docker Compose and Caddy deployment files
- OpenAPI sync into `shared/openapi`
- agentic docs under `docs/FEATURES`, `docs/TASKS`, `docs/PROMPTS`, and `docs/DECISIONS`
Socialize already has a larger FastEndpoints backend and Vue app. Preserve that implementation while adopting the scaffold.
## Files Likely To Change
- `backend/Socialize.slnx`
- `backend/src/Socialize.Api/**`
- `backend/tests/Socialize.Tests/**`
- `scripts/**`
- `deploy/caddy/Caddyfile`
- `docker-compose.yml`
- `docs/**`
- `README.md`
- `AGENTS.md`
- `.github/workflows/backend-ci.yml`
- `frontend/package.json`
- `frontend/scripts/fetch-openapi.mjs`
- `frontend/src/api/schema.d.ts`
## Constraints
- Preserve existing product code.
- Do not convert the frontend to TypeScript in this task.
- Do not rewrite backend modules into minimal API folders in this task.
- Do not introduce new secrets.
## Done When
- [x] Backend implementation moved under `backend/src/Socialize.Api`
- [x] Backend solution points at the new project path
- [x] Test project scaffold exists
- [x] Root scripts exist
- [x] OpenAPI sync command exists
- [x] Agentic docs/specs/tasks/prompts exist
- [x] Backend build passes
- [x] Frontend build passes
## Validation Commands
```bash
dotnet build backend/Socialize.slnx
dotnet test backend/Socialize.slnx
cd frontend && npm run build
```

View File

@@ -0,0 +1,39 @@
# Task: Document content state machine
## Feature
`docs/FEATURES/workspace-review-workflow.md`
## Goal
Define the current and intended content item states, transitions, and approval side effects before further workflow implementation.
## Context
The code already contains content items, approvals, comments, assets, notifications, and review queue screens. The workflow needs one durable spec so future agents do not infer state transitions from scattered UI code.
## Files Likely To Change
- `docs/FEATURES/workspace-review-workflow.md`
- `docs/FEATURES/content-approval-workflow.md`
- optionally `docs/DECISIONS/*.md`
## Constraints
- Documentation-only task.
- Do not change backend or frontend code.
- Distinguish current behavior from proposed behavior.
## Done When
- [ ] States are listed
- [ ] Allowed transitions are listed
- [ ] Actor permissions are listed
- [ ] Notification side effects are listed
- [ ] Open questions are explicit
## Validation Commands
```bash
git diff -- docs/FEATURES docs/DECISIONS
```