docs: v1.0 parity sweep — gttsize deprecation, model-store note, cognee retirement, memory-delete gate - #46
Open
thinmintdev wants to merge 1 commit into
Open
docs: v1.0 parity sweep — gttsize deprecation, model-store note, cognee retirement, memory-delete gate#46thinmintdev wants to merge 1 commit into
thinmintdev wants to merge 1 commit into
Conversation
…ination Ports the hal0-side docs/v1-parity-sweep fix (Hal0ai/hal0, same branch name) forward into this repo's mirrored copies, so the next mirror-docs sync doesn't clobber it. Scoped to only the four target issues' own facts — does not sync unrelated drift between this branch's base (upstream/master@e1cef95) and hal0's current docs; see PR description / agent report for the divergence inventory. - #1081 (getting-started/baremetal-ubuntu.mdx, getting-started/proxmox-lxc.mdx): GTT sizing guidance drops amdgpu.gttsize from the GRUB example/table, uses ttm.pages_limit=32505856 as the sole knob, and adds a deprecation Aside covering the amdttm.pages_limit out-of-tree-TTM-module equivalent and the modinfo check to tell which applies. - #985 (guides/configure.mdx, guides/enable-memory.mdx, reference/config-schema.mdx): the 'cognee' memory-engine value is retired (schema now rejects it, docs updated to match); removed enable-memory.mdx's "Migrate a legacy store" section, which documented a `hal0 memory migrate --cognee-dir` flag that doesn't exist in the current CLI. - #1083 (getting-started/first-model.mdx): added a "Where the pull lands" note covering [models].store / the legacy pull_root fallback / --storage-dir, inserted standalone since this branch's first-model.mdx still describes the pre-#1082 bundle-picker first-run flow (see report for why #1084's fresh-box-state content was NOT ported here). Also ports two files from Hal0ai/hal0 branch fix/memory-delete-hardening (a different, concurrent lane) since they document a real, just-landed API behavior change and belong in the same coherent docs PR: - reference/api/rest-api.mdx: /api/memory is ADMIN-classed end-to-end; DESTRUCTIVE_MEMORY_ROUTES pins the irreversible subset above the generic prefix rule. - reference/mcp-tools.mdx: the memory_delete bulk-delete arity gate applies identically on both the /mcp/memory and /mcp/admin mounts. Verified: npx astro check — 5 pre-existing errors in src/content.config.ts (zod version mismatch between astro and starlight-blog) and src/pages/changelog.astro (implicit-any), confirmed present at this branch's HEAD before these changes too (stash-tested) — none touch the 8 files changed here. npm run build — 57 pages built clean, all 8 changed pages present in the output, 0 errors. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Deploying hal0-web with
|
| Latest commit: |
bbefaf4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7fb7f9e7.hal0-web.pages.dev |
| Branch Preview URL: | https://docs-v1-parity-sweep.hal0-web.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upstream half of the docs work in
Hal0ai/hal0PR #1364.docs/**there is a mirror of this repo, so these edits must land here or the nextmirror-docs.ymlsync clobbers them.Path mapping verified against
mirror-docs.yml:src/content/docs/docs/**→ hal0sdocs/**(flat, doubled segment stripped,rsync --delete, excludinginternal/andREADME.md).Changes
baremetal-ubuntu.mdx,proxmox-lxc.mdx: upstream still had the dual-param GRUB line (amdgpu.gttsize=126976 ttm.pages_limit=32505856) and "keep it equal to gttsize" prose. Nowttm.pages_limit-only, dropped table row, deprecation Aside namingamdttm.pages_limitfirst-model.mdx: added the "Where the pull lands" Aside ([models].store,pull_rootfallback,--storage-dir)configure.mdx,enable-memory.mdx,config-schema.mdx: cognee dropped from the engine enum description; removed the "Migrate a legacy store" section documenting a--cognee-dirflag that never existed in this branchs CLI eitherreference/api/rest-api.mdx,reference/mcp-tools.mdx: document the/mcp/memorybulk-delete approval gate, which hal0 PR #1359 makes real. Upstreams pre-edit text was confirmed to match that branchs diff context verbatim before applyingNot ported, deliberately
#1084 cannot land upstream yet. This repos
first-model.mdxstill says the installer seeded the registry — #1084s "fresh box has zero models" premise contradicts that sentence directly. Both #1083 and #1084 are filed as blocked by #1082, and #1082s rewrite was never ported here. #1082 is the actual blocker.Also skipped: the
honcho-memory.mdxcross-link added in hal0 (that page does not exist here — would dangle).Pre-existing divergence found, not fixed
This repos
masterhas drifted well behind hal0s docs — slotrole/chatnaming vsagent/utility, ADR-0014 vs ADR-0023, missing proxmoxgid=passthrough values, missing "Point hal0 at your model storage" and "Troubleshooting" sections. That is a much larger reconciliation than these four issues and is noted, not attempted.Verification
Zero overlap with
fix/web-install-parity-and-manifests(diffed against master directly).🤖 Generated with Claude Code