docs: explicitly document tasks-template support in resolution stack

Author: Nimraakram12

docs/reference/presets.md

@@ -139,6 +139,8 @@ catalogs:
 
 Presets can provide command files, template files (like `plan-template.md`), and script files. These are resolved at runtime using a **replace** strategy — the first match in the priority stack wins and is used entirely. Each file is looked up independently, so different files can come from different layers.
 
+The same resolution stack shown below for plan-template.md now applies identically to tasks-template.md.
+
 > **Note:** Additional composition strategies (`append`, `prepend`, `wrap`) are planned for a future release.
 
 The resolution stack, from highest to lowest precedence:
@@ -172,6 +174,8 @@ flowchart TB
 
 Within each layer, files are organized by type:
 
+Presets can provide command files, template files (like plan-template.md and tasks-template.md), and script files.
+
 | Type      | Subdirectory   | Override path                              |
 | --------- | -------------- | ------------------------------------------ |
 | Templates | `templates/`   | `.specify/templates/overrides/`            |