Drop the claim that gemdb file.py leaves the script's directory off sys.path

[MatiasFernandez]

What

Removes the claim, in the README ("One thing differs from python3…") and in docs/grail.md, that gemdb file.py does not put the script's directory on sys.path, so a script cannot import a file next to it. The limitation no longer exists, so this PR deletes both mentions and adds nothing to replace them.

Where the claim came from

• Commit the scripts the Brain Freeze transcripts were run with, and the PRD they implement #21 (2026-09-07) first recorded it, while writing up Brain Freeze, and filed it upstream as Grail #847 ("importlib runPath: leaves sys.path empty").
• Tweak CLAUDE.md: cut noise, split out on-demand docs #37 moved it unchanged from CLAUDE.md into docs/grail.md.
• Rewrites to the README file #49 (2026-09-23) copied it into the README. Update the README for 1.5.3's traceback and install-failure changes #67 reworded it into the sentence removed here.

Why it no longer holds

• Grail #847 was closed as completed on 2026-09-07. The closing comment says it was fixed on Grail main by 8c8f503e ("Populate sys.path at startup…", 2026-08-29), which adds importlib class >> ___installScriptDir___:.
• That comment also mentioned a remaining gap: the directory was added as a relative path. Grail #854 ("Make sys.path[0] absolute, and give -m the working directory") fixed it and was merged the same day.
• vendor-pins.sh pins Grail beef473, and both 8c8f503e and #854's merge commit 203b481 are its ancestors (checked with the GitHub compare API).
• GemTalk/brain-freeze already dropped the claim (3ffee35, ef5cf1e). Its tools/seed.py now says "gemdb tools/seed.py puts this directory on sys.path".

How it was tested

I ran the installed gemdb (GemDB Python (beef473, engine 4.0.0.a4)) on macOS arm64 against this layout:

app/helper.py   VALUE = 42
app/later.py    VALUE = 7
app/main.py

import os, sys
print("sys.path[0]:", sys.path[0])
import helper
print("helper.VALUE =", helper.VALUE)
os.chdir("/")
import later
print("after chdir, later.VALUE =", later.VALUE)

Invocation	sys.path[0]	sibling import	import after os.chdir("/")	exit
gemdb app/main.py (relative path, from the parent dir)	absolute …/app	42	7	0
cd / && gemdb /abs/app/main.py	absolute …/app	42	7	0
python3 app/main.py (reference)	absolute …/app	42	7	—

The output was identical to python3's in every case.

README line 148 ("your own .py files can be imported once their directory is on sys.path") is still accurate and isn't changed.

🤖 Generated with Claude Code