diff --git a/actions/setup/js/check_workflow_timestamp_api.cjs b/actions/setup/js/check_workflow_timestamp_api.cjs
index cdc538a6fa..fc219e39f9 100644
--- a/actions/setup/js/check_workflow_timestamp_api.cjs
+++ b/actions/setup/js/check_workflow_timestamp_api.cjs
@@ -2,10 +2,12 @@
 /// <reference types="@actions/github-script" />
 
 /**
- * Check workflow lock file integrity using frontmatter hash validation.
+ * Check for a stale workflow lock file using frontmatter hash comparison.
  * This script verifies that the stored frontmatter hash in the lock file
- * matches the recomputed hash from the source .md file, regardless of
- * commit timestamps.
+ * matches the recomputed hash from the source .md file, detecting cases where
+ * the workflow was edited without recompiling the lock file. It does not
+ * provide tamper protection — use code review to guard against intentional
+ * modifications.
  *
  * Supports both same-repo and cross-repo reusable workflow scenarios:
  * - Primary: GitHub API (uses GITHUB_WORKFLOW_REF to identify source repo)
@@ -33,7 +35,7 @@ async function main() {
   const workflowMdPath = `.github/workflows/${workflowBasename}.md`;
   const lockFilePath = `.github/workflows/${workflowFile}`;
 
-  core.info(`Checking workflow lock file integrity using frontmatter hash:`);
+  core.info(`Checking for stale lock file using frontmatter hash:`);
   core.info(`  Source: ${workflowMdPath}`);
   core.info(`  Lock file: ${lockFilePath}`);
 
@@ -193,11 +195,11 @@ async function main() {
   if (!hashComparison) {
     // Could not compute hash - be conservative and fail
     core.warning("Could not compare frontmatter hashes - assuming lock file is outdated");
-    const warningMessage = `Lock file '${lockFilePath}' integrity check failed! Could not verify frontmatter hash for '${workflowMdPath}'. Run 'gh aw compile' to regenerate the lock file.`;
+    const warningMessage = `Lock file '${lockFilePath}' is outdated or unverifiable! Could not verify frontmatter hash for '${workflowMdPath}'. Run 'gh aw compile' to regenerate the lock file.`;
 
     let summary = core.summary
       .addRaw("### ⚠️ Workflow Lock File Warning\n\n")
-      .addRaw("**WARNING**: Lock file integrity check failed. Could not verify frontmatter hash.\n\n")
+      .addRaw("**WARNING**: Could not verify whether lock file is up to date. Frontmatter hash check failed.\n\n")
       .addRaw("**Files:**\n")
       .addRaw(`- Source: \`${workflowMdPath}\`\n`)
       .addRaw(`- Lock: \`${lockFilePath}\`\n\n`)
diff --git a/docs/src/content/docs/reference/frontmatter-hash-specification.md b/docs/src/content/docs/reference/frontmatter-hash-specification.md
index 286f59303b..16160765fd 100644
--- a/docs/src/content/docs/reference/frontmatter-hash-specification.md
+++ b/docs/src/content/docs/reference/frontmatter-hash-specification.md
@@ -10,9 +10,9 @@ This document specifies the algorithm for computing a deterministic hash of agen
 ## Purpose
 
 The frontmatter hash provides:
-1. **Change detection**: Verify that workflow configuration has not changed between compilation and execution
+1. **Stale lock detection**: Identify when the compiled lock file is out of sync with the source workflow (e.g. after editing the `.md` file without recompiling)
 2. **Reproducibility**: Ensure identical configurations produce identical hashes across languages (Go and JavaScript)
-3. **Security**: Detect unauthorized modifications to workflow frontmatter
+3. **Change detection**: Verify that workflow configuration has not changed between compilation and execution
 
 ## Hash Algorithm
 
@@ -196,8 +196,8 @@ Both Go and JavaScript implementations MUST:
 ## Security Considerations
 
 - The hash is **not cryptographically secure** for authentication (no HMAC/signing)
-- The hash **detects accidental or malicious changes** to frontmatter after compilation
-- The hash **does not protect** against modifications before compilation
+- The hash is designed to **detect stale lock files** — it catches cases where the frontmatter has changed since the lock file was last compiled
+- The hash **does not guarantee tamper protection**: anyone with write access to the repository can modify both the `.md` source and the `.lock.yml` file together, bypassing detection
 - Always validate workflow sources through proper code review processes
 
 ## Versioning