| 1 | # Tool Execute After Extensions DOX |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Own backend processing immediately after tool execution. |
| 6 | |
| 7 | ## Ownership |
| 8 | |
| 9 | - Ordered Python files own post-tool secret masking and future tool-result postprocessing. |
| 10 | |
| 11 | ## Local Contracts |
| 12 | |
| 13 | - Mask secrets before tool results reach history, UI, or model-visible context. |
| 14 | - Do not alter tool `break_loop` or response semantics unless the hook contract owns that behavior. |
| 15 | |
| 16 | ## Work Guidance |
| 17 | |
| 18 | - Coordinate with tool implementations and history hooks when changing tool result data. |
| 19 | |
| 20 | ## Verification |
| 21 | |
| 22 | - Smoke-test tool execution with sensitive output after changes. |
| 23 | |
| 24 | ## Child DOX Index |
| 25 | |
| 26 | No child DOX files. |