gitea
b15b495d2e
- Drive all approved tasks to completion with VERDICT.md - Fix state machine: IMPLEMENTATION.md was never checked in determine_task_state() - Fix state machine: DOC_REVIEW.md priority wrong (checked after BUG_REPORT) - Fix board display: approved planning tasks now advance to Design group - Fix board display: rejected planning tasks move to Blocked group - Fix path traversal: review API validated task names against ../ injection - Fix URL encoding: unquote() task names in API path parsing - Fix comment parsing: robust REVIEW.md read/write, handle falsy comments - Fix dead code: KanbanBoard class missing COLUMNS and __init__ - Fix inotify: explicit error messages and polling fallback - Fix review API: validate task names, prevent path traversal - Update CHANGELOG.md with all changes
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.
|