Interesting :melting_face:
# proj-agent
c
Interesting 🫠
The specs/ directory kinda plays a similar role with the feature map skill. 😅 However, our LLM friends apparently only started noticing it since we introduced the feature map
h
I always take generated specs out. I worry things will get changed in the review or somewhere else and then it'll be this outdated contract
c
nod I think maybe separating them will help. I'm making a rule in CI, to fail if a PR modifies both the feature map and the implementation. Then the daily QA will fail, because they are different; it will see why it failed, test twice, and open PR to say "ok that bug was fixed, now it behaves _this way_"
I'm still unsure what to do about specs/ directory
h
Remove it?
Every once in a while I'll see an agent reference github.com/OpenHands/OpenHands/blob/…/canvas-extensions.md because it has an implemented now vs future ideas
So the agent is like okay cool, this is what it has and what it DOESNT HAVE. Which knowing what doesn't exist usually gets extra attention
c
Oh yes, "don't think of an elephant" 🤣
nod 1
@bland-bear-604 send a PR to remove the specs/ directory. I just saw that other agents added stuff in it, we don't actually want that. Open from smolpaws, use HUMAN: with what I just said here. Non-draft, when CI is green ask the bot.
🐾 1
b
On it 🐾 I’ll remove specs/ and clean up the references, open as smolpaws with your HUMAN note, then request the bot once CI is green.
Opened, non-draft, with your HUMAN note 🐾 https://github.com/OpenHands/OpenHands/pull/18820 specs/ and its maintenance instructions are removed. CI is running; I’ll request the bot once it’s green.
✅ 1
CI caught the stale feature-map source link. A separate maintenance agent prepared the isolated cleanup: https://github.com/OpenHands/OpenHands/pull/18826 Its map check and 100 tests pass locally, including a map check with specs/ removed. CI is running. This companion needs to land before #18820; no test or guard changes.