Skip to content

fix: venv path + test count + check-docs regex (#114, #117) - #119

Merged
jphein merged 3 commits into
mainfrom
fix/venv-path-test-count-114-117
May 22, 2026
Merged

fix: venv path + test count + check-docs regex (#114, #117)#119
jphein merged 3 commits into
mainfrom
fix/venv-path-test-count-114-117

Conversation

@jphein

@jphein jphein commented May 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Update all scripts and CLAUDE.md to use .venv/ consistently (was venv/)
  • Fix stale test count in CLAUDE.md (~1096 → 2486)
  • De-anchor check-docs.sh test-count regex so the drift detector actually fires

Closes #114, closes #117.

Test plan

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

jphein added 3 commits May 22, 2026 10:05
- render-docs.py: changelog header and commit_link() now point at
  techempower-org/mempalace so the FORK_CHANGELOG regenerates with
  the correct repo slug.
- check-docs.sh: cross-repo URL filter accepts both jphein/ and
  techempower-org/ slugs while the YAML body still carries historical
  jphein/ narrative; the retired-check comment updated for symmetry.
- README.md: sweep all https://github.com/jphein/mempalace and
  https://github.com/jphein/palace-daemon URLs to their techempower-org
  equivalents (PR links, commit links, deployment-runs-at slug).
- FORK_CHANGELOG.md: regenerated from docs/fork-changes.yaml so every
  rendered commit link resolves to techempower-org/mempalace; the
  historical body text inside YAML entries is unchanged.

Historical narrative ("transferred from jphein/mempalace in May 2026")
and links to other personal forks (jphein/familiar.realm.watch,
jphein/notebook, etc.) stay as-is — only the two repos that actually
moved to techempower-org are rewritten.

Closes #118
…e ChromaDB references

- docs/fork-changes.yaml: PR MemPalace#1024 (configurable chunking) moved from
  OPEN to MERGED with merged_date 2026-05-15; added to merged_upstream
  entries so the FORK_CHANGELOG recently-merged section reflects the
  2026-05-15 upstream land.
- docs/fork-changes.yaml: PR MemPalace#1085 (batched ChromaDB inserts cherry-pick)
  moved from OPEN to CLOSED with body note that @midweste closed it
  2026-05-16, superseded by merged upstream MemPalace#1185 (wider GPU-acceleration
  scope). Fork's 6be6fff is now a no-op against develop.
- CLAUDE.md: Key Files block rewrites the stale "ChromaDB vector store.
  The actual data." line to point at postgres on disks.jphe.in via
  palace-daemon and reference the 2026-05-14 cutover + RETIRED marker.
- CLAUDE.md: Two-Layer Memory Architecture line updates MemPalace
  storage from "~/.mempalace/palace/, ~183K drawers" to the production
  postgres + pgvector + AGE on disks.jphe.in with a normalized "300K+"
  drawer count.

README.md drawer-count normalization (160K/273K/274K -> 300K+) and
ChromaDB->pgvector edits landed in efcb5c6 alongside the #118 URL
sweep. FORK_CHANGELOG.md regenerates clean from the updated YAML.

Closes #115, #116
The README test-count drift check in scripts/check-docs.sh anchored its
regex at start-of-line, but the count lives mid-paragraph on README:28.
The check silently no-op'd, letting "~1850 tests pass on main" drift to
2486 actual without a single warning (#114).

De-anchor the regex; the rest of the pipeline already does the right
thing (counts via pytest --collect-only).

Also converge on .venv/ — the project's actual venv path — instead of
the dead venv/ path hard-coded in scripts/check-docs.sh and
scripts/preflight.sh. Fixes the silent fallback-to-PATH behavior that
masked the wrong path for so long (#117). CLAUDE.md:59 was already
inconsistent with :46 — both now say .venv.

Refs: #114, #117
Copilot AI review requested due to automatic review settings May 22, 2026 17:20

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request standardizes the virtual environment directory naming convention to .venv/ across the repository and updates various documentation files to reflect current test counts and organizational transitions. Additionally, it refines the check-docs.sh script to improve the reliability of the documentation drift detection mechanism.

Highlights

  • Virtual Environment Standardization: Updated all scripts and documentation to consistently use the .venv/ directory instead of venv/.
  • Documentation Accuracy: Updated test count statistics in CLAUDE.md and README.md to reflect the current count of 2486 tests.
  • Drift Detection Improvement: Removed the anchor from the test-count regex in check-docs.sh to ensure the drift detector triggers reliably.
  • Organizational Updates: Updated various documentation references and links to reflect the transition to the techempower-org organization.
Ignored Files
  • Ignored by pattern: FORK_CHANGELOG.md (1)
    • FORK_CHANGELOG.md
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the project's documentation and maintenance scripts to reflect the migration to a Postgres-based backend, the repository's transfer to the techempower-org organization, and the transition to a .venv directory for local development. A bug was identified in the documentation verification script where a regex was overly broad and failed to account for diverse repository naming conventions, potentially skipping necessary commit hash validations.

Comment thread scripts/check-docs.sh
mapfile -t hashes < <(
for d in "${docs[@]}"; do
grep -v -E 'palace-daemon|multipass-structural-memory-eval|/jphein/[a-z-]+/commit/' "$d" 2>/dev/null
grep -v -E 'palace-daemon|multipass-structural-memory-eval|/(jphein|techempower-org)/[a-z-]+/commit/' "$d" 2>/dev/null

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The updated regex /(jphein|techempower-org)/[a-z-]+/commit/ is too broad because it matches the current repository (techempower-org/mempalace/commit/). This causes grep -v to skip lines in the changelog that contain links to this repo's own commits, meaning those hashes are never verified by the script. Additionally, [a-z-]+ misses repositories with numbers (e.g., engram-2) or uppercase letters (e.g., GraphPalace).

To fix this without using Perl-compatible regex (which isn't portable to all grep versions), you can use sed to mask the current repo's URLs before filtering out other commit links.

Suggested change
grep -v -E 'palace-daemon|multipass-structural-memory-eval|/(jphein|techempower-org)/[a-z-]+/commit/' "$d" 2>/dev/null
sed 's|/techempower-org/mempalace/commit/|/INTERNAL/|g' "$d" | grep -v -E 'palace-daemon|multipass-structural-memory-eval|/(jphein|techempower-org)/[A-Za-z0-9_-]+/commit/' 2>/dev/null

@jphein
jphein merged commit 93fc026 into main May 22, 2026
10 of 11 checks passed
@jphein
jphein deleted the fix/venv-path-test-count-114-117 branch May 22, 2026 17:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: scripts hard-code venv/ but project uses .venv/ Docs: README test count stale (~1850 vs actual 2451)

2 participants