Conversation
…onoun detection; add tests
…; clarify Codex workflow
…ate STATUS & Design Intent
…lper in docs README
…ensure valid JSON-style object with anthropic-version=2023-06-01
…; keep aiden headers fix intact
![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 suggestions.
Reply with @codex fix comments to fix any unresolved comments.
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, or 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 fix this CI failure" or "@codex address that feedback".
| home = /usr/bin | ||
| include-system-site-packages = false | ||
| version = 3.12.3 | ||
| executable = /usr/bin/python3.12 | ||
| command = /usr/bin/python3 -m venv /home/michael/soulfield/.venv |
There was a problem hiding this comment.
[P1] Keep .venv out of repository history
The commit adds the entire .venv virtual environment, e.g. pyvenv.cfg and thousands of site‑packages. These files are machine‑specific build artefacts; tracking them inflates the repo by hundreds of thousands of lines and couples builds to a single developer’s environment. The Python dependencies should be captured in requirements.txt and regenerated locally, not committed.
Useful? React with 👍 / 👎.
|
|
||
| const ROOT = path.resolve(__dirname, ".."); | ||
| const RESULTS = path.join(ROOT, "workspace", "data", "infranodus", "results"); | ||
| const SPECS = path.join(ROOT, ".agent-os", "specs"); | ||
| // Write specs where the safe executor and tests expect them |
There was a problem hiding this comment.
[P1] Spec generator now writes to backend path only
Changing SPECS to backend/.agent-os/specs means sf specify:infra will generate specs under backend/.agent-os/..., but helper tooling such as tools/infra still ingests from ~/.agent-os/specs. New specs will no longer be imported into InfraNodus because they are written to a different directory than the importer reads. Either update the importer paths or maintain a copy/symlink so the old location stays in sync.
Useful? React with 👍 / 👎.
|
Closing - this PR is based on a very old repository snapshot and contains 100+ files. The changes are no longer relevant to current main. |
1 participant
Title:
Summary
Checklist
Validation
1.
2.
Links