Development record
abcd should find out what the forge can do instead of asking the person or assuming. On 2026-10-16, setting up a throwaway lab to test abcd land, the agent asked the product thinker whether the team organisation allowed private copies; the product thinker did not know and should not have to. A read-only query answered it (members_can_fork_private_repositories is false for the organisation's own repositories), and a real attempt showed a private fork of a repository the person owns works anyway. The general want: abcd tests the forge's functionality itself (can repositories be private, can they be forked privately, is a merge queue available) and goes with the route that delivers the wanted outcome; only when no route exists does it ask, offering the options. Likely an intent; it needs a state-of-the-art pass on forge capability detection.
abcd should find out what the forge can do instead of asking the person or assuming. On 2026-10-16, setting up a throwaway lab to test abcd land, the agent asked the product thinker whether the team organisation allowed private copies; the product thinker did not know and should not have to. A read-only query answered it (members_can_fork_private_repositories is false for the organisation's own repositories), and a real attempt showed a private fork of a repository the person owns works anyway. The general want: abcd tests the forge's functionality itself (can repositories be private, can they be forked privately, is a merge queue available) and goes with the route that delivers the wanted outcome; only when no route exists does it ask, offering the options. Likely an intent; it needs a state-of-the-art pass on forge capability detection.
Frontmatter
| id | iss-2610161632245527 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610161632245527-abcd-should-find-out-what-the-forge-can.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610161647248332abcd finds out what the forge can do before choosing a routerelated
mentions1
- iss-2610292103166339abcd ahoy --remote decides that a setting is owed by the plan from the repository being private or internal and from GitHub's refusal text containing the word upgrade, not from the owner's plan. The fidelity review of itd-2610290746077716 (rcp-6083de2cef52) found its scope condition cond-2610290749118129 (a setting the plan or the visibility does not offer is reported as owed) narrowed: a refusal GitHub words any other way reads as unknown, though never as a failure (internal/core/ahoy/remote_baseline.go:452, remote_baseline.go:236). iss-2610161632245527, which asks abcd to probe what the forge allows before picking a route, is the wider form of this.