Close out 0003's open items: link #53, decide the release asset - #54
Merged
Conversation
The design doc left repository custom properties as prose, with an availability caveat that has since been answered — the org's property endpoints respond, nothing is defined yet. Link #53 and say what that issue actually has to decide, which is the App permission, not availability. NO-ISSUE: backlink to #53, per AGENTS.md section 4 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CgLE8cg9huy2EZnRoXhmwp
It sat under Open items as undecided, but it isn't: the tag already addresses the exact file and rollout.yml reads it by checking the tag out, so an asset would be a fourth copy of something reachable three ways. State it in Design with the condition that would change the answer. NO-ISSUE: closes out an open item from 0003 with the decision already taken Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CgLE8cg9huy2EZnRoXhmwp
gavinbee
added
the
no-issue
gavinbee
marked this pull request as ready for review
September 6, 2026 14:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Tidies
0003's Open items, which came out of #51 carrying two entries that were no longer accurate.Custom properties → #53. The entry said the idea "needs the property defined at org level first" and left availability as the thing to confirm. Availability is confirmed — the org's endpoints respond, with nothing defined yet:
So the entry now links the issue and names what that issue actually has to settle: whether
swimblocks-reconciler, which is installed org-wide, should hold a Custom properties write permission.AGENTS.md§4 wants an aspirational item pointing at an issue rather than sitting as prose.Release asset → decided, moved into Design. This was recorded as open but is a no. The tag already addresses the exact file (
git show <tag>:.github/settings.yml, or the contents API with?ref=<tag>), androllout.ymlreads it by checking the tag out, so an asset would be a fourth copy of something reachable three ways. It now sits in Design as a decision, with the condition that would change the answer — something outside git needing the file by URL — and the contrast withswim-club-tech-survey, where the attached CSV is the product people come to the release page for.That leaves one genuine open item, the rollout failure policy, which is recorded as intended behaviour rather than a question.
Testing
Docs only — no code touched.
ruff check .andpytest -qunaffected.Checklist
no-issueruff check .clean (Python repos) — n/a, no code changedNO-ISSUE: design-doc bookkeeping following #51 and #53
🤖 Generated with Claude Code