get-tbd 0.1.29 → 0.2.0

package/dist/docs/guidelines/typescript-code-coverage.md

@@ -7,8 +7,8 @@ author: Joshua Levy (github.com/jlevy) with LLM assistance
 
 **Last Updated**: 2026-05-21
 
-**Tracks**: Vitest `^4.1.7`, `@vitest/coverage-v8` `^4.1.7`. Vitest 5.0 is in
-beta — do not adopt yet.
+**Tracks**: Vitest `^4.1.7`, `@vitest/coverage-v8` `^4.1.7`. Vitest 5.0 is in beta — do
+not adopt yet.
 
 **Related**:
 
@@ -86,16 +86,16 @@ Low branch coverage often indicates untested error paths and edge cases.
 pnpm add -D vitest@^4.1 @vitest/coverage-v8@^4.1
 ```
 
-Follow the [14-day package-age rule](./pnpm-monorepo-patterns.md#supply-chain-mitigation)
-on every upgrade: use `ncu --cooldown 14` or
-`pnpm install --frozen-lockfile`.
+Follow the
+[14-day package-age rule](./pnpm-monorepo-patterns.md#supply-chain-mitigation) on every
+upgrade: use `ncu --cooldown 14` or `pnpm install --frozen-lockfile`.
 
 ### Vitest 4.x changes that affect coverage
 
 - **`coverage.all` was removed** in Vitest 4. Use `coverage.include` and
   `coverage.exclude` to define exactly which files are reported.
-- Coverage reporters and v8 provider now ship as part of `@vitest/coverage-v8`
-  aligned with the Vitest major version — pin them together.
+- Coverage reporters and v8 provider now ship as part of `@vitest/coverage-v8` aligned
+  with the Vitest major version — pin them together.
 
 ### Example Configuration
 
@@ -194,3 +194,7 @@ Vitest automatically fails when thresholds are not met if configured.
 - **Don’t test implementation details**: Focus on public APIs and behavior
 - **Don’t ignore branch coverage**: TypeScript’s type system creates many branches
 - **Don’t exclude too much**: Be selective about exclusions
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/guidelines/typescript-rules.md

@@ -9,9 +9,9 @@ alwaysApply: true
 
 **Last Updated**: 2026-05-21
 
-**Tracks**: TypeScript `^6.0.3` (stable). TypeScript 7.0 Beta
-(`@typescript/native-preview`, binary `tsgo`) is available but **not yet
-production-ready** — do not adopt for shipped builds.
+**Tracks**: TypeScript `^6.0.3` (stable).
+TypeScript 7.0 Beta (`@typescript/native-preview`, binary `tsgo`) is available but **not
+yet production-ready** — do not adopt for shipped builds.
 
 **Related**:
 
@@ -21,9 +21,9 @@ production-ready** — do not adopt for shipped builds.
 - [TypeScript Code Coverage](./typescript-code-coverage.md)
 - [pnpm Monorepo Patterns](./pnpm-monorepo-patterns.md) and
   [Bun Monorepo Patterns](./bun-monorepo-patterns.md)
-- [Supply-Chain Mitigation](./pnpm-monorepo-patterns.md#supply-chain-mitigation) —
-  the 14-day package-age rule applies to every TypeScript dependency
-  (`zod`, `commander`, `vitest`, `eslint`, type packages, etc.).
+- [Supply-Chain Mitigation](./pnpm-monorepo-patterns.md#supply-chain-mitigation) — the
+  14-day package-age rule applies to every TypeScript dependency (`zod`, `commander`,
+  `vitest`, `eslint`, type packages, etc.).
 
 ## Coding Style
 
@@ -424,3 +424,7 @@ production-ready** — do not adopt for shipped builds.
   import { writeFile } from 'atomically';
   await writeFile(filePath, content);
   ```
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/guidelines/typescript-sorting-patterns.md

@@ -232,3 +232,7 @@ items.sort(
     .result(),
 );
 ```
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/guidelines/typescript-yaml-handling-rules.md

@@ -8,9 +8,9 @@ globs: "*.ts"
 
 **Last Updated**: 2026-05-21
 
-**Tracks**: `yaml@^2.8.4` (latest stable; 2026-05-02). The `yaml@3.0.0-1`
-release is tagged `next` (pre-release) — do not adopt yet. Zod 4.x is the
-recommended validation companion.
+**Tracks**: `yaml@^2.8.4` (latest stable; 2026-05-02). The `yaml@3.0.0-1` release is
+tagged `next` (pre-release) — do not adopt yet.
+Zod 4.x is the recommended validation companion.
 
 **Related**:
 
@@ -205,3 +205,7 @@ const output = `---\n${stringifyYaml(data)}---\n\n${content}`;
 
 - For general TypeScript rules, see `tbd guidelines typescript-rules`
 - For error handling patterns, see `tbd guidelines error-handling-rules`
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/install/ensure-gh-cli.sh

@@ -1,17 +1,38 @@
 #!/bin/bash
 # Automated GitHub CLI setup for Claude Code sessions
 # This script runs on SessionStart to ensure gh CLI is available and authenticated
+#
+# Supply-chain policy (see SUPPLY-CHAIN-SECURITY.md): the gh version is PINNED to
+# a release at least 14 days old, and every download is verified against a pinned
+# SHA-256 checksum. Do NOT change this to fetch "latest" from the API at runtime;
+# that bypasses the cool-off window. To bump the pin, pick a release that is >=14
+# days old and copy its checksums from:
+#   https://github.com/cli/cli/releases/download/v<VERSION>/gh_<VERSION>_checksums.txt
 
-set -e
+set -euo pipefail
 
 # Add common binary locations to PATH
 export PATH="$HOME/.local/bin:$HOME/bin:/usr/local/bin:$PATH"
 
+# Pinned gh release (>=14 days old per supply-chain cool-off) and its checksums.
+GH_VERSION="2.92.0"
+
+# SHA-256 checksums from gh_2.92.0_checksums.txt, keyed by asset suffix.
+checksum_for() {
+    case "$1" in
+        linux_amd64.tar.gz) echo "b57848131bdf0c229cd35e1f2a51aa718199858b2e728410b37e89a428943ec4" ;;
+        linux_arm64.tar.gz) echo "c2248526dd0160c08d3fccca2332c3c1a07c15a78b23978e77735f1b5a18cfee" ;;
+        macOS_amd64.zip)    echo "ae9bb327ab0d91071bdada79f8f14034a2a0f19b0e001835a782eafa519d2af0" ;;
+        macOS_arm64.zip)    echo "b11c54f6bd7d15ed6590475079e5b2fcf36f45d3991a80041b29c9d0cc1f1d07" ;;
+        *) echo "" ;;
+    esac
+}
+
 # Check if gh is already installed
 if command -v gh &> /dev/null; then
     echo "[gh] CLI found at $(which gh)"
 else
-    echo "[gh] CLI not found, installing..."
+    echo "[gh] CLI not found, installing pinned v${GH_VERSION}..."
 
     # Detect platform
     OS=$(uname -s | tr '[:upper:]' '[:lower:]')
@@ -19,38 +40,52 @@ else
     [ "$ARCH" = "x86_64" ] && ARCH="amd64"
     [ "$ARCH" = "aarch64" ] && ARCH="arm64"
 
-    echo "[gh] Detected platform: ${OS}_${ARCH}"
-
-    # Get latest version from GitHub API (with fallback)
-    GH_VERSION=$(curl -fsSL https://api.github.com/repos/cli/cli/releases/latest 2>/dev/null \
-        | grep -o '"tag_name": *"v[^"]*"' | head -1 | sed 's/.*"v\([^"]*\)".*/\1/')
-
-    # Fallback version if API fails
-    GH_VERSION=${GH_VERSION:-2.83.1}
-
-    echo "[gh] Version: ${GH_VERSION}"
-
-    # Build download URL based on platform
+    # Build the asset suffix and archive type per platform.
     if [ "$OS" = "darwin" ]; then
-        DOWNLOAD_URL="https://github.com/cli/cli/releases/download/v${GH_VERSION}/gh_${GH_VERSION}_macOS_${ARCH}.zip"
+        PLATFORM="macOS_${ARCH}.zip"
         ARCHIVE_EXT="zip"
+        EXTRACT_DIR="/tmp/gh_${GH_VERSION}_macOS_${ARCH}"
     else
-        DOWNLOAD_URL="https://github.com/cli/cli/releases/download/v${GH_VERSION}/gh_${GH_VERSION}_${OS}_${ARCH}.tar.gz"
+        PLATFORM="${OS}_${ARCH}.tar.gz"
         ARCHIVE_EXT="tar.gz"
+        EXTRACT_DIR="/tmp/gh_${GH_VERSION}_${OS}_${ARCH}"
     fi
 
+    echo "[gh] Detected platform: ${PLATFORM}"
+
+    EXPECTED=$(checksum_for "$PLATFORM")
+    if [ -z "$EXPECTED" ]; then
+        echo "[gh] ERROR: no pinned checksum for platform ${PLATFORM}; refusing to install"
+        echo "[gh] Add the checksum from gh_${GH_VERSION}_checksums.txt to this script"
+        exit 1
+    fi
+
+    ASSET="gh_${GH_VERSION}_${PLATFORM}"
+    DOWNLOAD_URL="https://github.com/cli/cli/releases/download/v${GH_VERSION}/${ASSET}"
+
     echo "[gh] Downloading from ${DOWNLOAD_URL}..."
+    curl -fsSL -o "/tmp/${ASSET}" "$DOWNLOAD_URL"
 
-    # Download
-    curl -fsSL -o "/tmp/gh.${ARCHIVE_EXT}" "$DOWNLOAD_URL"
+    # Verify the download against the pinned checksum before extracting.
+    if command -v sha256sum &> /dev/null; then
+        ACTUAL=$(sha256sum "/tmp/${ASSET}" | awk '{print $1}')
+    else
+        ACTUAL=$(shasum -a 256 "/tmp/${ASSET}" | awk '{print $1}')
+    fi
+    if [ "$ACTUAL" != "$EXPECTED" ]; then
+        echo "[gh] ERROR: checksum mismatch for ${ASSET}"
+        echo "[gh]   expected ${EXPECTED}"
+        echo "[gh]   actual   ${ACTUAL}"
+        rm -f "/tmp/${ASSET}"
+        exit 1
+    fi
+    echo "[gh] Checksum verified for ${ASSET}"
 
     # Extract based on archive type
     if [ "$ARCHIVE_EXT" = "zip" ]; then
-        unzip -q "/tmp/gh.zip" -d /tmp
-        EXTRACT_DIR="/tmp/gh_${GH_VERSION}_macOS_${ARCH}"
+        unzip -q "/tmp/${ASSET}" -d /tmp
     else
-        tar -xzf "/tmp/gh.tar.gz" -C /tmp
-        EXTRACT_DIR="/tmp/gh_${GH_VERSION}_${OS}_${ARCH}"
+        tar -xzf "/tmp/${ASSET}" -C /tmp
     fi
 
     # Install to ~/.local/bin (works in cloud and local)
@@ -59,7 +94,7 @@ else
     chmod +x ~/.local/bin/gh
 
     # Clean up
-    rm -rf "${EXTRACT_DIR}" "/tmp/gh.${ARCHIVE_EXT}"
+    rm -rf "${EXTRACT_DIR}" "/tmp/${ASSET}"
 
     echo "[gh] Installed to ~/.local/bin/gh"
 fi
@@ -72,7 +107,7 @@ if ! command -v gh &> /dev/null; then
 fi
 
 # Check authentication status
-if [ -n "$GH_TOKEN" ]; then
+if [ -n "${GH_TOKEN:-}" ]; then
     # GH_TOKEN is set, verify it works
     if gh auth status &> /dev/null; then
         echo "[gh] Authenticated successfully"

package/dist/docs/shortcuts/standard/agent-handoff.md

@@ -57,3 +57,7 @@ References: packages/llm-pricing/ - see scripts/generate-llms-data.ts and src/_g
 
 Setup: Run `pnpm install` after pulling (new dependencies added).
 ```
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/checkout-third-party-repo.md

@@ -48,3 +48,7 @@ need.
 - The `attic/` directory is gitignored—cloned repos won’t pollute your project
 - You can clone multiple repos into attic/ as needed
 - Delete cloned repos when done to save disk space
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/code-cleanup-all.md

@@ -88,3 +88,7 @@ cycle afterwords, fixing all build or test issues.
     - Batch database queries instead of individual fetches in loops
 
     - Consolidate nested sequential queries into single `Promise.all` call
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/code-cleanup-docstrings.md

@@ -75,3 +75,7 @@ export function formatContextMarkdown(
 4. Review existing docstrings and remove any that are redundant or obvious
 
 5. Run linting to ensure no syntax errors
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/code-cleanup-tests.md

@@ -56,3 +56,7 @@ Keep tests that:
 4. Remove trivial tests while preserving meaningful coverage
 
 5. Run the full test suite to ensure no regressions
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/code-review-and-commit.md

@@ -42,3 +42,7 @@ Create a to-do list with the following items then perform all of them:
      CI watch.
    - Only proceed when you see all checks have passed.
    - Confirm to the user that CI has passed.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/coding-spike.md

@@ -52,3 +52,7 @@ Create a to-do list with the following items then perform all of them:
    ```
 
 9. Report findings and recommend next steps.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/create-or-update-pr-simple.md

@@ -55,3 +55,7 @@ Create a to-do list with the following items then perform all of them:
    - Only proceed when you see all checks have passed in the final summary.
 
 8. Confirm to the user that CI has passed and the PR is ready for review.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/create-or-update-pr-with-validation-plan.md

@@ -74,3 +74,7 @@ Create a to-do list with the following items then perform all of them:
    - Only proceed when you see all checks have passed in the final summary.
 
 8. Confirm to the user that CI has passed and the PR is ready for review.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/implement-beads.md

@@ -28,3 +28,7 @@ Create a to-do list with the following items then perform all of them:
 4. Repeat this for all beads where you know how to fix them.
    If unsure about a bead, let the user know at the end of all work which beads had
    problems.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/merge-upstream.md

@@ -28,3 +28,7 @@ Merge upstream changes from origin/main into the current branch.
 6. **Verify**: Run formatting, linting, and tests
    - Fix any issues introduced by the merge
    - Commit the merge result
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/new-architecture-doc.md

@@ -29,3 +29,7 @@ Create a to-do list with the following items then perform all of them:
    If designing new architecture, iterate with the user on the design.
 
 5. Summarize the architecture and ask the user to review.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/new-guideline.md

@@ -122,3 +122,7 @@ description: Best practices for designing TypeScript APIs including naming, type
 | `{lang}-{topic}-rules` | `typescript-cli-tool-rules` | Specialized patterns |
 | `{domain}-rules` | `convex-rules` | Framework/platform rules |
 | `general-{topic}-rules` | `general-testing-rules` | Language-agnostic rules |
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/new-plan-spec.md

@@ -47,3 +47,7 @@ Create a to-do list with the following items then perform all of them:
 
 5. To list beads linked to a spec, use `tbd list --spec` (see `tbd list --help` for
    details on filtering and path matching).
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/new-qa-playbook.md

@@ -57,3 +57,7 @@ Create a to-do list with the following items then perform all of them:
    - Mark phases ✅/❌ in the status table after each run
    - Add test results with dates in the “Test Results” section
    - Archive or update playbooks when they become stale
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/new-research-brief.md

@@ -28,3 +28,7 @@ Create a to-do list with the following items then perform all of them:
    Ask the user for guidance when you need clarification or hit decision points.
 
 5. Summarize findings and ask the user to review.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/new-shortcut.md

@@ -77,3 +77,7 @@ For official shortcuts added to `packages/tbd/docs/shortcuts/standard/`:
 - **Guidelines**: Rules to reference (knowledge)
 
 See `tbd shortcut new-guideline` for creating guidelines.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/new-validation-plan.md

@@ -85,3 +85,7 @@ This serves as both a testing checklist and a summary for PR reviewers, showing:
    - Both
 
 6. **Summarize** what’s validated vs what remains for the user to review.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/plan-implementation-with-beads.md

@@ -54,3 +54,7 @@ If unclear, ask the user if they want you to create a spec first using
 - **Blocker** (`tbd dep add`): Sequential ordering.
   A bead cannot start until its blockers are complete.
   Use for tasks that genuinely depend on prior work.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/precommit-process.md

@@ -62,3 +62,7 @@ Create a to-do list with the following items then perform all of them:
    (See `tbd guidelines commit-conventions` for details.)
    If all checks pass, commit directly.
    Only ask the user if there are unresolved problems.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/review-code-python.md

@@ -32,3 +32,7 @@ Create a to-do list with the following items then perform all of them:
    - List Python-specific issues found (if any) with file:line references
    - Suggest specific fixes
    - Note any Python patterns that should be addressed
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/review-code-typescript.md

@@ -32,3 +32,7 @@ Create a to-do list with the following items then perform all of them:
    - List TypeScript-specific issues found (if any) with file:line references
    - Suggest specific fixes
    - Note any TypeScript patterns that should be addressed
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/review-code.md

@@ -107,3 +107,7 @@ Create a to-do list with the following items then perform all of them:
    - Otherwise, present the review and ask:
      - **Fix issues**: Create tbd beads for issues and begin fixing
      - **Report only**: Just output the review (no changes)
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/review-github-pr.md

@@ -139,3 +139,7 @@ Create a to-do list with the following items then perform all of them:
     - List any beads created (if fixing with beads)
     - Confirm CI status
     - Provide the PR URL
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/revise-all-architecture-docs.md

@@ -20,3 +20,7 @@ Run `tbd prime` for more on using tbd and current status.
 4. Work through each child bead, close when done
 
 5. Close epic with summary
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/revise-architecture-doc.md

@@ -28,3 +28,7 @@ Review and update an architecture document to ensure accuracy with current code.
 6. **Add Future Considerations section** with:
    - **Open Questions**: Possible bugs, issues, or design uncertainties
    - **Potential Improvements**: Ideas for future enhancements
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/setup-github-cli.md

@@ -75,3 +75,7 @@ See `docs/general/agent-setup/github-cli-setup.md` for token creation instructio
 | `gh auth status` shows errors | GH_TOKEN not set or invalid |
 | `Bad credentials` | Token expired or lacks permissions |
 | `Resource not accessible` | Token lacks required scopes (need repo, workflow) |
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/sync-failure-recovery.md

@@ -67,3 +67,7 @@ For detailed troubleshooting, workspace usage, and diagnostic commands, see:
 ```bash
 tbd guidelines tbd-sync-troubleshooting
 ```
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/update-specs-status.md

@@ -25,3 +25,7 @@ Review all active specs and ensure tbd issues accurately reflect current progres
    `docs/project/specs/done/`
 
 5. **Sync**: Run `tbd sync` to push all changes
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/shortcuts/standard/welcome-user.md

@@ -63,3 +63,7 @@ Here are examples of things you can say and what happens:
 
 Then ask if they’d like to explore any of tbd’s capabilities or get started on
 something.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

package/dist/docs/tbd-closing.md

@@ -29,3 +29,7 @@ Every session must end with tbd in a clean state:
 **Work is not done until pushed, CI passes, and tbd is synced.**
 
 > **Tip**: Run `tbd closing` anytime for this checklist.
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->