docs: point public project links to Anionex - #10
Conversation
There was a problem hiding this comment.
Pull request overview
Updates project documentation and metadata to reflect the public GitHub repository location and to improve Windows installation guidance.
Changes:
- Repointed multiple documentation/support links from
dsh-external/dsh-vision-toolkittoAnionex/dsh-vision-toolkit. - Removed “private repo access” prerequisites from Quick start sections.
- Added Windows installation notes (autocrlf, WindowsApps Python stubs, out-of-tree dependency resolution).
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| SUPPORT.md | Updates issue/PR and issue-chooser URLs to the public GitHub org. |
| README.md | Fixes release/clone/issues links and adds Windows install notes. |
| README.zh.md | Mirrors README updates for Chinese documentation, including Windows notes. |
| package.json | Updates repository and bugs metadata to the public GitHub org. |
| CHANGELOG.md | Updates compare/release reference URLs to the public GitHub org. |
| .github/ISSUE_TEMPLATE/config.yml | Updates support link to the public GitHub org. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
a3f326f to
cf945a3
Compare
Update the public README, landing page, support, issue-template, changelog, and package metadata links to the live Anionex repository. Keep the npm package scope unchanged and extend the portable gate so retired repository URLs cannot return on public surfaces. Drop the Windows checkout and dependency workarounds from the original proposal because PR Anionex#14 fixed both in the package. The existing Python override documentation already covers interpreter discovery after PR Anionex#4 made bootstrap resolution explicit. Co-Authored-By: DeepSeek Harness <noreply@deepseek.com>
cf945a3 to
3d4705b
Compare
Anionex
changed the title
|
Closing this PR: the underlying Windows install issues have been fixed at the code level by #13 and #14 (scoped schemastery peer import, byte-preserved vendored snapshot, Windows trace/UTF-8 contracts), which supersede the documentation workarounds proposed here. The repo-URL cleanup can be handled separately by the maintainers if still wanted (note: index.html and scripts/verify-portable.mjs still reference the old org). Thanks for the quick fixes! |
Summary
Anionex/dsh-vision-toolkitwhile keeping the npm package name@dsh-external/dsh-vision-toolkitunchanged.0.1.0-0.1.2changelog links, because those historical tags remain only in the former private repository. The currentv0.1.4public release remains owned bymain.scripts/verify-portable.mjsto validate the new package metadata and reject the retired public repository URL across the public project surfaces.Windows guidance review
The original Windows notes were removed rather than rewritten:
core.autocrlfbefore cloning.gitattributesbyte preservation and a realcore.autocrlf=truecheckout regression to the portable gate.uv; the existingruntime.pythonreference already documents the supported override. #13 separately enforces UTF-8 subprocess and trace contracts.No Windows workaround section remains in the diff.
Copilot inline comments
index.htmlstill used the old repository: fixed all six landing-page occurrences.scripts/verify-portable.mjsexpected the old metadata: fixed and covered with a retired-URL regression check.autocrlfcommand comments are superseded because the obsolete workaround was removed entirely.All four comments are addressed by the updated diff.
Verification
Passed:
git diff --check vision-upstream/main...HEADnpm run verify:portable— 26 required files, 21 JavaScript files, 24 images; includesnpm pack --dry-run --ignore-scriptsv0.1.4release, and historical changelog commit ranges — all returned200Full TypeScript build/tests are not claimed from this isolated out-of-tree worktree. The package's TypeScript configuration intentionally resolves DSH source types through sibling
../packagesand../vendorpaths. A build attempt with the available newer local DSH facade failed on pre-existing API type mismatches, and standalone dependency installation failed because the@deepseek-ai/dsh-*peer packages are not published at the declared^0.0.1ranges. The dependency-free portable/package gate above is the relevant acceptance path for this documentation and verifier-only change.This PR has not been merged.