From 0e88049d59124abfab0bf1bc57b5ee32d0430afb Mon Sep 17 00:00:00 2001
From: N0zoM1z0 <161784452+N0zoM1z0@users.noreply.github.com>
Date: Wed, 11 Nov 2026 06:06:48 +0000
Subject: [PATCH] fix(docs): pin the NTFS extension fixture source link

Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
---
 docs/verification/ntfs-metadata-2026-11-11.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/verification/ntfs-metadata-2026-11-11.md b/docs/verification/ntfs-metadata-2026-11-11.md
index dae53afe37..d74b56ea73 100644
--- a/docs/verification/ntfs-metadata-2026-11-11.md
+++ b/docs/verification/ntfs-metadata-2026-11-11.md
@@ -195,7 +195,7 @@ resident attribute-list graphs into acquired extension metadata. Physical facts
 and their aggregate counts stay separate from bounded linked facts. Journal
 and extension joins share the producer-owned record identity verdict.
 
-The [source-built extension fixture](../../tests/fixtures/ntfsMftExtension.ts)
+The [source-built extension fixture](https://github.com/morluto/rea/blob/b76b9716192db1f2bbfdcbb093bb01c29a7e8d10/tests/fixtures/ntfsMftExtension.ts)
 contains base slot 0 / sequence 2 and extension slot 1 / sequence 7. The base
 list refers to the extension's FILE_NAME attribute ID 3; the extension declares
 base reference `(0, 2)`. Dissect 3.16 independently verified both physical