feat(docs): enhance README with interactive result links and references

- add links to interactive HTML results for storage format evaluation and foreign-key architecture study
- update descriptions in README to reflect the new structure of research documents
- clarify the contents of the research directory in the README

docs/rules/code-data-formatting.md

@@ -78,8 +78,6 @@ an en-dash.
   content, not typographic substitutions. UTF-8 throughout is the right
   answer. (Repository artifacts are English; this matters only for quoted
   material.)
-- **Imported reference materials** in `docs/examples/` are kept verbatim as
-  received; they are not binding documents.
 
 ## 4. Detection / enforcement
 
@@ -89,8 +87,7 @@ future detector is documented here so it can be built consistently:
 
 - **What it flags.** Any occurrence of the Unicode codepoints in the section 1
   substitution table inside in-scope files. The section 3 exemptions
-  (scientific notation, international content, `docs/examples/`) are the only
-  carve-outs.
+  (scientific notation, international content) are the only carve-outs.
 - **Exit behavior.** Non-zero exit when any flagged codepoint is found under
   the scan roots, so it can later gate a commit hook or a build step.
 - **Tooling.** When this detector is created it MUST be a PowerShell script