revert: restore crates/vite_task/docs to main

The docs edits in this PR (task-cache.md, terminologies.md) are not
necessary for the task command shorthand feature; reverting to keep
the PR scope tight.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: wan9chi

crates/vite_task/docs/task-cache.md

@@ -550,13 +550,13 @@ Ensure commands produce identical outputs for identical inputs:
 
 ```json
 {
-  "tasks": {
-    "build": ["tsc", "rollup -c", "terser dist/bundle.js"]
+  "scripts": {
+    "build": "tsc && rollup -c && terser dist/bundle.js"
   }
 }
 ```
 
-Each `&&` separated command is cached independently. Task command arrays use the same granular caching semantics. If only terser config changes, TypeScript and rollup will hit cache.
+Each `&&` separated command is cached independently. If only terser config changes, TypeScript and rollup will hit cache.
 
 ## Implementation Reference
 

crates/vite_task/docs/terminologies.md

@@ -16,24 +16,19 @@
 // vite-task.json
 {
   "tasks": {
-    "lint": "echo lint",
-    "check": ["eslint .", "tsc --noEmit", "prettier --check ."],
-  },
+    "lint": {
+    "command": "echo lint"
+  }
 }
 ```
 
-In the example above, `build`, `lint`, and `check` are **task group names**. A task group may define one task, or multiple tasks separated by `&&`.
-
-In `tasks`, command-only task groups can be written as a string or as an array. Object form with `command` and options is also supported.
+In the example above, `build` and `lint` are **task group names**. A task group may define one task, or multiple tasks separated by `&&`.
 
-The three task groups generate these tasks:
+The two task groups generates 3 tasks:
 
 - `app#build(subcommand 0)` (runs `echo build1`)
 - `app#build` (runs `echo build2`)
 - `app#lint` (runs `echo lint`)
-- `app#check(subcommand 0)` (runs `eslint .`)
-- `app#check(subcommand 1)` (runs `tsc --noEmit`)
-- `app#check` (runs `prettier --check .`)
 
 These are **task names**. They are for displaying and filtering.