From 011a2456c27bff207a6c018fd9d804ce1373714f Mon Sep 17 00:00:00 2001 From: mahdahar <89adham@gmail.com> Date: Mon, 9 Mar 2026 16:49:03 +0700 Subject: [PATCH] Cleanup: Remove obsolete docs, opencode configs, and openspec files; update test models and API docs --- .opencode/command/opsx-apply.md | 149 - .opencode/command/opsx-archive.md | 154 - .opencode/command/opsx-explore.md | 170 - .opencode/command/opsx-propose.md | 103 - .../skills/openspec-apply-change/SKILL.md | 156 - .../skills/openspec-archive-change/SKILL.md | 114 - .opencode/skills/openspec-explore/SKILL.md | 288 - .opencode/skills/openspec-propose/SKILL.md | 110 - .../memories/code_style_and_conventions.md | 223 + .../memories/equipmentlist/seeder-merged.md | 22 + .serena/memories/equipmentlist/seeder.md | 32 + .serena/memories/task_completion.md | 129 + app/Models/Test/TestDefGrpModel.php | 2 +- app/Models/Test/TestDefSiteModel.php | 2 +- docs/ERD_EXTRACT.md | 1129 ---- docs/FRONTEND_TEST_MANAGEMENT_PROMPT.md | 1581 ----- docs/Use Case_260214.docx | Bin 47672 -> 0 bytes docs/audit-logging-plan.md | 762 --- docs/clqms_database.dbdiagram | 1914 ------ docs/clqms_database.dbml | 640 -- docs/manual-result-entry-plan.md | 941 --- docs/mvp_plan.md | 249 - ...laboratory quality management system_3c.md | 5152 ----------------- docs/test-types-reference.md | 434 -- docs/use_case_260214.md | 514 -- .../2026-03-08-backend-specs/.openspec.yaml | 2 - .../2026-03-08-backend-specs/QUICKSTART.md | 74 - .../2026-03-08-backend-specs/README.md | 55 - .../code-templates/Routes-additions.php | 42 - .../SpecimenController-delete-method.php | 49 - .../code-templates/UserController.php | 290 - .../code-templates/UserModel.php | 138 - .../2026-03-08-backend-specs/design.md | 165 - .../2026-03-08-backend-specs/proposal.md | 63 - .../specimen-delete.md | 119 - .../archive/2026-03-08-backend-specs/tasks.md | 92 - .../2026-03-08-backend-specs/user-api.md | 243 - openspec/config.yaml | 20 - public/api-docs.bundled.yaml | 34 + public/components/schemas/tests.yaml | 34 + 40 files changed, 476 insertions(+), 15914 deletions(-) delete mode 100644 .opencode/command/opsx-apply.md delete mode 100644 .opencode/command/opsx-archive.md delete mode 100644 .opencode/command/opsx-explore.md delete mode 100644 .opencode/command/opsx-propose.md delete mode 100644 .opencode/skills/openspec-apply-change/SKILL.md delete mode 100644 .opencode/skills/openspec-archive-change/SKILL.md delete mode 100644 .opencode/skills/openspec-explore/SKILL.md delete mode 100644 .opencode/skills/openspec-propose/SKILL.md create mode 100644 .serena/memories/code_style_and_conventions.md create mode 100644 .serena/memories/equipmentlist/seeder-merged.md create mode 100644 .serena/memories/equipmentlist/seeder.md create mode 100644 .serena/memories/task_completion.md delete mode 100644 docs/ERD_EXTRACT.md delete mode 100644 docs/FRONTEND_TEST_MANAGEMENT_PROMPT.md delete mode 100644 docs/Use Case_260214.docx delete mode 100644 docs/audit-logging-plan.md delete mode 100644 docs/clqms_database.dbdiagram delete mode 100644 docs/clqms_database.dbml delete mode 100644 docs/manual-result-entry-plan.md delete mode 100644 docs/mvp_plan.md delete mode 100644 docs/prj_clinical laboratory quality management system_3c.md delete mode 100644 docs/test-types-reference.md delete mode 100644 docs/use_case_260214.md delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/.openspec.yaml delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/QUICKSTART.md delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/README.md delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/code-templates/Routes-additions.php delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/code-templates/SpecimenController-delete-method.php delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/code-templates/UserController.php delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/code-templates/UserModel.php delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/design.md delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/proposal.md delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/specimen-delete.md delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/tasks.md delete mode 100644 openspec/changes/archive/2026-03-08-backend-specs/user-api.md delete mode 100644 openspec/config.yaml diff --git a/.opencode/command/opsx-apply.md b/.opencode/command/opsx-apply.md deleted file mode 100644 index 94b8c1e..0000000 --- a/.opencode/command/opsx-apply.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -description: Implement tasks from an OpenSpec change (Experimental) ---- - -Implement tasks from an OpenSpec change. - -**Input**: Optionally specify a change name (e.g., `/opsx-apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes. - -**Steps** - -1. **Select the change** - - If a name is provided, use it. Otherwise: - - Infer from conversation context if the user mentioned a change - - Auto-select if only one active change exists - - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select - - Always announce: "Using change: " and how to override (e.g., `/opsx-apply `). - -2. **Check status to understand the schema** - ```bash - openspec status --change "" --json - ``` - Parse the JSON to understand: - - `schemaName`: The workflow being used (e.g., "spec-driven") - - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others) - -3. **Get apply instructions** - - ```bash - openspec instructions apply --change "" --json - ``` - - This returns: - - Context file paths (varies by schema) - - Progress (total, complete, remaining) - - Task list with status - - Dynamic instruction based on current state - - **Handle states:** - - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx-continue` - - If `state: "all_done"`: congratulate, suggest archive - - Otherwise: proceed to implementation - -4. **Read context files** - - Read the files listed in `contextFiles` from the apply instructions output. - The files depend on the schema being used: - - **spec-driven**: proposal, specs, design, tasks - - Other schemas: follow the contextFiles from CLI output - -5. **Show current progress** - - Display: - - Schema being used - - Progress: "N/M tasks complete" - - Remaining tasks overview - - Dynamic instruction from CLI - -6. **Implement tasks (loop until done or blocked)** - - For each pending task: - - Show which task is being worked on - - Make the code changes required - - Keep changes minimal and focused - - Mark task complete in the tasks file: `- [ ]` → `- [x]` - - Continue to next task - - **Pause if:** - - Task is unclear → ask for clarification - - Implementation reveals a design issue → suggest updating artifacts - - Error or blocker encountered → report and wait for guidance - - User interrupts - -7. **On completion or pause, show status** - - Display: - - Tasks completed this session - - Overall progress: "N/M tasks complete" - - If all done: suggest archive - - If paused: explain why and wait for guidance - -**Output During Implementation** - -``` -## Implementing: (schema: ) - -Working on task 3/7: -[...implementation happening...] -✓ Task complete - -Working on task 4/7: -[...implementation happening...] -✓ Task complete -``` - -**Output On Completion** - -``` -## Implementation Complete - -**Change:** -**Schema:** -**Progress:** 7/7 tasks complete ✓ - -### Completed This Session -- [x] Task 1 -- [x] Task 2 -... - -All tasks complete! You can archive this change with `/opsx-archive`. -``` - -**Output On Pause (Issue Encountered)** - -``` -## Implementation Paused - -**Change:** -**Schema:** -**Progress:** 4/7 tasks complete - -### Issue Encountered - - -**Options:** -1.