Observation from cycle 208
During the post-merge audit of issue #208, the repository-scoped Copilot agent was absent from .github/agents/inquiry.agent.md and iq doctor reported:
- copilot: agent not deployed
- Run 'inquiry init' to deploy agent
The bounded corpus does not support a precise answer to when the file disappeared:
- .github/agents/inquiry.agent.md is gitignored in the repo root
- git log --all --name-status -- .github/agents/inquiry.agent.md returns no history
- git reflog --all -- .github/agents/inquiry.agent.md returns no file-specific evidence
The current code makes the lifecycle asymmetric but opaque:
- iq init deploys .github/agents/inquiry.agent.md
- iq target clean deletes .github/agents/inquiry.agent.md
- iq uninstall deletes .github/agents/inquiry.agent.md
So the file can disappear through legitimate local commands, but the cycle currently leaves no durable, auditable trace that explains which command last created or removed it.
Why this matters
After a real Inquiry cycle, the repo cannot answer a basic operational question from evidence: whether the repo-scoped agent was never redeployed, was deleted by target clean, was deleted by uninstall, or was removed manually.
That makes iq doctor diagnostically correct but forensically weak.
Requested outcome
Make the repo-scoped agent lifecycle auditable. One acceptable direction would be to add an explicit, inspectable local status surface for the repo agent, or otherwise make init / target clean / uninstall leave enough evidence that a later audit can answer:
- was the repo agent deployed for this repo?
- which command last changed that state?
- when did that change occur?
Observation from cycle 208
During the post-merge audit of issue #208, the repository-scoped Copilot agent was absent from .github/agents/inquiry.agent.md and iq doctor reported:
The bounded corpus does not support a precise answer to when the file disappeared:
The current code makes the lifecycle asymmetric but opaque:
So the file can disappear through legitimate local commands, but the cycle currently leaves no durable, auditable trace that explains which command last created or removed it.
Why this matters
After a real Inquiry cycle, the repo cannot answer a basic operational question from evidence: whether the repo-scoped agent was never redeployed, was deleted by target clean, was deleted by uninstall, or was removed manually.
That makes iq doctor diagnostically correct but forensically weak.
Requested outcome
Make the repo-scoped agent lifecycle auditable. One acceptable direction would be to add an explicit, inspectable local status surface for the repo agent, or otherwise make init / target clean / uninstall leave enough evidence that a later audit can answer: