cleanup: remove stale .mindmodel, old venvs, orphaned code, and transient artifacts
Removes: - .mindmodel/ directory and related CI workflows (mindmodel-schedule.yml, mindmodel-validation.yml) - scripts/mindmodel/ and scripts/validate_mindmodel.py - src/types/ and src/validators/ (orphaned type modules, only used by mindmodel) - tests/ci/, tests/scripts/mindmodel/, tests/types/, tests/validators/ (mindmodel-only tests) - thoughts/ledgers/ and thoughts/shared/ (stale transient directories) - .venv_axis and .venv_plotly (orphaned virtual environments, ~1.1 GB) - outputs/blog-charts/ (stale generated HTML files) - data/*.json sidecars (empty cache artifacts) - __pycache__ and *.pyc files across repo Updates: - .gitignore: remove thoughts/shared/analyses/ entry Space reclaimed: ~1.1 GB+
This commit is contained in:
@@ -1,40 +0,0 @@
|
||||
# 2026-03-28 Ansible package implementation
|
||||
|
||||
Summary of changes added to repository:
|
||||
|
||||
- packages/@ansible/example/
|
||||
- package.json (scoped package @ansible/example)
|
||||
- README.md
|
||||
- src/index.js
|
||||
- tests/ (test_package_json.js, test_pack_inspect.js, _pack_helpers.js, run.js)
|
||||
- .github/workflows/publish-ansible-example.yml
|
||||
- .github/workflows/deploy-motief.yml
|
||||
- docs/deployment/ansible-package-deploy.md
|
||||
- docs/embeddings.md
|
||||
- README.md (top-level)
|
||||
- thoughts/shared/changes/2026-03-28-ansible-package-implementation.md (this file)
|
||||
|
||||
Verification commands (run from repo root):
|
||||
|
||||
1. Run package tests:
|
||||
cd packages/@ansible/example && npm test
|
||||
|
||||
2. Run pack inspection:
|
||||
cd packages/@ansible/example && node tests/test_pack_inspect.js
|
||||
|
||||
3. Simulate pack locally:
|
||||
cd packages/@ansible/example && npm pack && tar -tzf <produced-tgz> | head -n 20
|
||||
|
||||
4. Check workflows syntax locally (optional):
|
||||
- Use `act` or `nektos/act` to run workflow_dispatch triggers in a container; ensure secrets are not printed.
|
||||
|
||||
5. Verify docs updated for embeddings and deployment: open docs/embeddings.md and docs/deployment/ansible-package-deploy.md
|
||||
|
||||
Notes:
|
||||
- Do NOT add secrets to repo. Secrets: NPM_TOKEN, DEPLOY_SSH_KEY, DEPLOY_HOST, DEPLOY_USER, DEPLOY_SSH_PORT, OPENROUTER_API_KEY
|
||||
|
||||
Contact: Sven Geboers
|
||||
|
||||
End of changelog.
|
||||
|
||||
Write the file with neutral tone and concise steps for verification.
|
||||
@@ -1,36 +0,0 @@
|
||||
---
|
||||
date: 2026-03-28
|
||||
title: "Remove .env from tracking — report"
|
||||
---
|
||||
|
||||
Summary
|
||||
-------
|
||||
|
||||
I removed `.env` from the repository index and added it to `.gitignore` to prevent accidental future commits. This was a non-destructive, forward-facing change — the repository history still contains prior commits that touched `.env`.
|
||||
|
||||
What I ran
|
||||
-----------
|
||||
|
||||
- git rm --cached .env
|
||||
- ensured `.gitignore` contains `.env`
|
||||
- committed the change: chore(secrets): stop tracking .env and add to .gitignore
|
||||
|
||||
Commits that referenced .env
|
||||
----------------------------
|
||||
|
||||
These commits touched `.env` in the repository history (from git log --all -- .env):
|
||||
|
||||
- 35f4667 2026-03-28 Sven Geboers chore(secrets): stop tracking .env and add to .gitignore
|
||||
- 3551a82 2026-03-21 Sven Geboers feat(analysis): add 2D political compass and 2D trajectories
|
||||
|
||||
Notes
|
||||
-----
|
||||
|
||||
- The `.env` file was removed from the index but remains in historical commits. If you need to remove it from history, we can perform a history rewrite (git-filter-repo or BFG) and force-push; this is destructive and requires coordination.
|
||||
- I created a CI guard to fail builds if a `.env` file is present in the repository root (see .github/workflows/forbid-env.yml). This prevents accidental re-adding via pushes/PRs.
|
||||
|
||||
Next steps (recommended)
|
||||
------------------------
|
||||
|
||||
1. Rotate secrets that might have been in `.env` (see the secrets-rotation checklist next). This is mandatory if those keys were used anywhere publicly or in shared CI.
|
||||
2. If you require history purge, reply confirming and I'll prepare a filter-repo run and the exact force-push sequence.
|
||||
@@ -1,25 +0,0 @@
|
||||
---
|
||||
date: 2026-03-28
|
||||
title: "Secrets rotation checklist"
|
||||
---
|
||||
|
||||
Rotate these secrets if they were stored in `.env` or otherwise exposed:
|
||||
|
||||
- OPENROUTER_API_KEY / OPENAI_API_KEY
|
||||
- NPM_TOKEN
|
||||
- DEPLOY SSH keys or passwords (DEPLOY_SSH_KEY, DEPLOY_PASSWORD)
|
||||
- Any database credentials, API keys, or third-party service tokens
|
||||
|
||||
Steps
|
||||
-----
|
||||
|
||||
1. Revoke the current tokens in each provider's dashboard.
|
||||
2. Create new tokens/keys and store them in the repository secrets (GitHub Settings → Secrets).
|
||||
3. Update any running services / CI variables to use the new tokens.
|
||||
4. If you used SSH keys and replaced them, update the authorized_keys on the VPS and remove the old key.
|
||||
|
||||
Verification
|
||||
------------
|
||||
|
||||
- Use CI dry-run jobs that check connectivity and token validity.
|
||||
- Run local commands that use the new tokens.
|
||||
Reference in New Issue
Block a user