docs: align FESA agents with minimal reference cases
This commit is contained in:
@@ -21,7 +21,9 @@ Read these first:
|
||||
|
||||
## Workflow
|
||||
|
||||
1. For planning, convert upstream documents into small ordered tasks and test ids.
|
||||
1. For planning, use the project-local `harness` skill to convert upstream documents into a
|
||||
user-approved multi-Step draft. Create `phases/` files only after approval and never run the
|
||||
executor without a separate explicit request.
|
||||
2. For implementation, follow `RED -> GREEN -> VERIFY`.
|
||||
3. RED: write the planned unit, integration, parser/I/O, or reference-comparison test first.
|
||||
4. RED: run the targeted test and verify the expected failure before production code.
|
||||
@@ -71,6 +73,8 @@ uv run --with pytest python -m pytest -v -rs
|
||||
- Do not run Abaqus, Nastran, or any reference solver.
|
||||
- Do not generate or modify Abaqus reference CSV files.
|
||||
- Do not approve release readiness.
|
||||
- During planning, do not block on canonical reference naming, README, metadata, provenance, or
|
||||
an unrequested reference portfolio. Require only feature-declared input/CSV files, matching, and tolerance.
|
||||
|
||||
## Quality Gate
|
||||
|
||||
|
||||
Reference in New Issue
Block a user