~/.dsh/AGENTS.md should not be the global AGENTS.md

[hjiang]

Right now, the official agent-instructions plugin uses ~/.dsh/AGENTS.md as the global instructions file. This makes it impossible to create a project-specific AGENTS.md for ~/.dsh.

In contrast, the pi coding agent uses the following rule:

• ~/.pi/AGENTS.md is the project-specific AGENTS.md for Pi's configuration
• ~/.pi/agent/AGENTS.md is the global AGENTS.md

Something similar should work better for dsh.

[denial123789]

Source-verified on rc.7 (99f6f02): this collision is real, and it affects more than naming.

The current loader has two independent rules:

1. USER_GLOBAL_FILE is fixed to AGENTS.md, resolved under the plugin's dshHome (normally $DSH_HOME / ~/.dsh).
2. Project discovery defaults to AGENTS.md, CLAUDE.md plus the local overlays. If no configured root marker is found while walking upward, findProjectRoot() falls back to the Session cwd.

So when the Session cwd is $DSH_HOME, the same physical path can carry both meanings: fixed user-global instructions and the workspace-root AGENTS.md candidate. The renderer's dedup is per displayed directory, not a global same-absolute-path dedup, so operators should not assume the duplicate meaning is automatically collapsed.

A separate fixed global path, as proposed here, would restore a useful invariant:

• $DSH_HOME/AGENTS.md: project instructions when working on the DSH configuration directory
• a distinct path such as $DSH_HOME/agent/AGENTS.md: user-global instructions

A migration would need to define backward compatibility, because moving the default silently would make existing global policy disappear. The baseline identity already includes discovery and precedence configuration, so a changed path/config can correctly append a superseding baseline rather than rewriting history.

Until that ships, the safe operator rule is to treat $DSH_HOME/AGENTS.md as global only. Use a direct task instruction, an explicit Skill, or a separate version-controlled configuration workspace for DSH-home-specific guidance. Do not use symlink tricks: final-component instruction symlinks are intentionally followed and can cross the repository trust boundary.

I mapped the verified baseline order, local overlays, nested structured-fs discovery, refresh behavior, budget eviction, and this collision here:
https://sandbaseai.github.io/deepseek-harness-handbook/deepseek-harness-agents-md.html

Disclosure: independent community guide, verified against rc.7; it does not imply the proposed path split is already released.