both clear now
This commit is contained in:
@@ -31,10 +31,9 @@ Arbitrarily altering database schemas or changing S3 key namespaces (e.g., forci
|
||||
- **Weak Response**: Introduces duplicate model definitions, breaks S3 object-key conventions, or mutates shared Mongoose schemas across multiple worker directories without an evidenced upstream schema contract or producer coordination.
|
||||
|
||||
|
||||
##### Persistence
|
||||
- **Strong Response**: Delivers a functional repair that handles both message envelope shapes, documents contract assumptions, and thoroughly investigates relevant codebase state.
|
||||
- **Weak Response**: Halts completely upon discovering that pro_v2 is absent on current HEAD without attempting a basic transport repair, or quits after fixing only one of duplicate schema files.
|
||||
|
||||
### Persistence
|
||||
- **Strong Response**: Pushes through codebase confusion to deliver a working transport fix (`job._doc ?? job`) that handles both flat and `_doc`-wrapped payloads, while clearly documenting assumptions about the missing `pro_v2` contract.
|
||||
- **Weak Response**: Halts prematurely or quits upon discovering that `pro_v2` is absent on current HEAD without attempting a basic transport repair for the SQS worker crash.
|
||||
|
||||
### Communication
|
||||
- **Strong Response**: Clearly explains transport envelope normalization (`job._doc ?? job`). Explicitly highlights the ambiguity surrounding `pro_v2` between current working HEAD and past git commit history in plain, professional language.
|
||||
|
||||
Reference in New Issue
Block a user