docs: add portfolio context recovery note#114
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c6cd0c0e47
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - Lockfile rationale when lockfiles changed | ||
| - Screenshots for UI changes | ||
| 6. Performance checks required before release health is considered done: | ||
| 6. Performance checks required before done: |
There was a problem hiding this comment.
This makes the full performance suite mandatory before any task can be called done, and line 33 then blocks completion whenever one of those gates is not run. The previous wording scoped bundle/build/Lighthouse/API/DB/asset checks to release health, so a documentation-only or routine maintenance change now becomes impossible to complete without running release-level performance validation; keep these gates scoped to release validation or relevant performance-impacting changes.
Useful? React with 👍 / 👎.
| ## Current State | ||
|
|
||
| The repo is active product work. The README describes the intended support workflow, core search pipeline, and local privacy posture. Current local changes include unrelated dependency-lock work, so recovery edits should stay limited to documentation context unless the active branch owner explicitly broadens scope. |
There was a problem hiding this comment.
This portfolio context is committed as repo-wide agent guidance, but it describes transient local state (Current local changes include unrelated dependency-lock work) and tells future agents to limit recovery edits around that state. On a clean branch or after the dependency-lock work is resolved, agents following AGENTS.md will still behave as if unrelated local changes exist and may incorrectly avoid legitimate non-documentation work; keep this section limited to stable project context or move ephemeral recovery notes outside committed instructions.
Useful? React with 👍 / 👎.
1 participant
What
Adds a managed portfolio-context block to AGENTS.md.
Why
This closes one dirty-worktree item in the GithubRepoAuditor context recovery plan while leaving unrelated local dependency-lock work untouched.
How
Documentation-only update based on the README and repo-local agent guidance.
Checklist
Testing
git diff --check