Turtle 8d62467823 docs(skills): one canonical resolution, no DSH_SOURCE ...

DSH_SOURCE is an install-time shell variable the installer never exports, so
a skill reading ${DSH_SOURCE} at runtime reads nothing. Verified unset in a
running dsh process.

Git resolves the main clone identically for every install, so the curl-vs-
adopted distinction was never a branch point in these workflows. Verified
one launcher-then-Git recipe against three shapes: a curl install cloning
into the container, an adopted clone nested far outside any container, and
a custom DSH_SOURCE container.

dsh-customize now states that single procedure and warns off the installer
variables. dsh-upgrade's Layout describes what the resolution finds rather
than a path convention, and no longer teaches install shapes as cases.

2026-07-31 22:29:53 +08:00

..

create-dsh-sdk-project

refactor(llm-deepseek)!: rename the provider route to deepseek-official

2026-07-29 16:36:07 +08:00

dsh-customize

docs(skills): one canonical resolution, no DSH_SOURCE

2026-07-31 22:29:53 +08:00

dsh-upgrade

docs(skills): one canonical resolution, no DSH_SOURCE

2026-07-31 22:29:53 +08:00

dsh-upstream-customization

feat(skills): bundle and harden personal maintenance workflows

2026-07-27 18:53:30 +08:00