[docs] fix table formatting in workflows README

- Improve table alignment and formatting for category prefixes
- Fix missing newline at end of file

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: snomiao

.github/workflows/README.md

@@ -6,16 +6,16 @@ Workflow files follow a consistent naming pattern: `<prefix>-<descriptive-name>.
 
 ### Category Prefixes
 
-| Prefix | Purpose | Example |
-|--------|---------|---------|
-| `ci-` | Testing, linting, validation | `ci-tests-e2e.yaml` |
-| `release-` | Version management, publishing | `release-version-bump.yaml` |
-| `pr-` | PR automation (triggered by labels) | `pr-claude-review.yaml` |
-| `types-` | TypeScript type generation | `types-registry-api.yaml` |
-| `i18n-` | Internationalization updates | `i18n-update-core.yaml` |
+| Prefix     | Purpose                             | Example                     |
+| ---------- | ----------------------------------- | --------------------------- |
+| `ci-`      | Testing, linting, validation        | `ci-tests-e2e.yaml`         |
+| `release-` | Version management, publishing      | `release-version-bump.yaml` |
+| `pr-`      | PR automation (triggered by labels) | `pr-claude-review.yaml`     |
+| `types-`   | TypeScript type generation          | `types-registry-api.yaml`   |
+| `i18n-`    | Internationalization updates        | `i18n-update-core.yaml`     |
 
 ## Documentation
 
 Each workflow file contains comments explaining its purpose, triggers, and behavior. For specific details about what each workflow does, refer to the comments at the top of each `.yaml` file.
 
-For GitHub Actions documentation, see [Events that trigger workflows](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows).
+For GitHub Actions documentation, see [Events that trigger workflows](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows).