12 lines
718 B
Markdown
12 lines
718 B
Markdown
|
# Adversarial Bug Report: Additive Extension Model
|
||
|
|
|
||
|
|
## Deep Review
|
||
|
|
The global-first read order in orchestrate.md is correct. The extension loading order (after global for prompts/contracts, before global for scripts) makes sense — scripts need pre-processing hooks.
|
||
|
|
|
||
|
|
## Potential Issues
|
||
|
|
1. **Extension conflict**: If two extensions define the same file, the later one silently wins. No merge logic exists. This is by design (additive overrides), but could confuse users.
|
||
|
|
|
||
|
|
2. **Script ordering**: Extensions loaded before global scripts (`pre-processing`). If a global script evolves and the extension was written for an older version, behavior could break silently.
|
||
|
|
|
||
|
|
## Verdict: PASS — no security or logic flaws.
|