Staged a new local orientation repo for Salesforce Litify Hubs work at /Users/samaguiar/Documents/Salesforce Litify Hubs.
Added these staged files: .gitignore, .env.example, README.md, AGENTS.md, docs/source-map.md, docs/current-attorney-hub-context.md, docs/qa-and-rollback.md, docs/session-log/2026-06-14-repo-staging.md, scripts/refresh-context.sh, and reports/.gitkeep.
The repo is designed as an agent-facing orientation and handoff layer, not a duplicate of the active Salesforce metadata repo. It explains where to start, how to verify live state, which skills to load, where the implementation repo currently lives, how to avoid stale Attorney Hub assumptions, and how to QA and rollback future work.
Live Salesforce CLI check confirmed LITIFY_ORG is connected as sam@kylawoffice.com. A live smoke query succeeded against litify_pm__Matter__c using SELECT Id, Name FROM litify_pm__Matter__c LIMIT 1.
The implementation repo was observed at /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project. It was on branch agent/attorney-hub-birthdays-2026-06-09, ahead of origin by 10 commits, with many modified and untracked files. No changes were made there.
QA completed: git diff --check passed, and scripts/refresh-context.sh ran successfully after one shell escaping fix for the $15k search pattern. The script writes ignored context reports under reports/context-refresh-*.md.
The requested local repo staging task was completed. The new files are staged in git but not committed. No live Salesforce metadata deployment or destructive action was needed.
A future agent can commit the staged repo if Sam wants a saved local baseline. A helpful next expansion would be adding a GitHub remote or cloud sync so other devices and agents can use the same orientation layer without relying on this machine's local path. If that cloud sync is approved, keep Notion as the stable source of truth and use environment variables for local path overrides.
Start in /Users/samaguiar/Documents/Salesforce Litify Hubs, read AGENTS.md, then run scripts/refresh-context.sh. Treat any paths in the docs as observations from 2026-06-14, not permanent truth. Before touching Salesforce source, inspect the active implementation repo status and avoid broad cleanup because it was already dirty and likely shared with other agents. For Attorney Hub work, load litify-workup, salesforce-workup, and attorney-hub-workup, then verify live org state before making claims.
Importance: Medium. Status: Done for local staging. Pending only if Sam wants a commit, GitHub remote, or cloud migration.