backends: point the project-settings source comment at its current anchor
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Read AGENTS.md and docs/decisions/README.md for the anchor/path/line convention. Run rg -n 'settingSources:' packages/ui-backend-claude/src/sdk-options.ts, then inspect the live comment at packages/ui-backend-claude/src/permission-hooks.ts:394 and sibling live comments citing sdk-options.ts. Done means the live citation points to the anchor's current line, sibling references are checked, and historical changelog text remains unchanged.
Written by the indexing model from the issue text.
Description
Context
Found during the #1429 source-comment citation audit. On main 82a64a13a08c44f2daef425d1a9df2c10840ea8e, the project-settings comment (// the brain repo's project settings, packages/ui-backend-claude/src/permission-hooks.ts:394) cites settingSources at sdk-options.ts:294. The actual anchor (settingSources, packages/ui-backend-claude/src/sdk-options.ts:295) is one line later; line 294 is the preceding comment.
The same mismatch exists on the baseline and the #1429 branch. That contribution does not move this anchor, so this is a standalone, nonblocking follow-up rather than a wrapper-propagation change. Searches for the exact stale pointer and open settingSources/citation reports found no duplicate. The older CHANGELOG entry about lines 90/96 is historical release evidence and should remain historical.
Scope
Correct the live source-comment citation to the current anchored source location and check sibling live references to the same file. Follow the anchor/path/line convention in AGENTS.md and docs/decisions/README.md.
Out of scope
Runtime behavior, permissions, project-settings selection, wrapper propagation, historical changelog rewriting, and a new citation framework.
Acceptance criteria
- The live comment's cited line starts on the
settingSourcesanchor in the source at implementation time. - Audit other live package comments citing sdk-options.ts; retain explicitly historical changelog observations.
- Keep the change documentation-only, with no runtime/API or package-version change.
Verification
Use rg -n 'settingSources:' packages/ui-backend-claude/src/sdk-options.ts and compare the live citation to that exact line. Run the ordinary required preflight before submitting. Existing docs citation tests do not establish package-comment coverage; no such coverage is claimed here.
Contract impact
None. A source-comment pointer correction; no consumer-visible behavior, supported API, CLI JSON, MCP or frontmatter change. No changeset or release commitment is selected by filing this unsorted backlog item. It is not a blocker for #1429 and is not being implemented in that work.
2026-10-20 triage at main af0547c2d4d197ed3766f2817cf56eb5f0486ab4: the live comment still cites sdk-options.ts:294 while settingSources starts at line 295; both the target and sibling source comments were inspected. The existing context, scope, exclusions, acceptance criteria, verification and no-contract-impact brief are complete. Priority p2 sorts this wanted, unscheduled documentation correction; no milestone is added. It remains standalone because correcting this source-comment pointer does not deliver the per-app isolation or public backend-seam outcomes of the existing epics. No implementation or runtime verification was performed.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 5h 45m
- Merged PRs (30d)
- 960
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from schlessera/brain-kit
-
agent-ready area: ci area: docs priority: p1 type: chore
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
schlessera/brain-kit#2951 ·
Maintainers usually reply within 1 day
-
agent-ready area: ci priority: p2 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
schlessera/brain-kit#2769 · 11 comments ·
Maintainers usually reply within 1 day
-
agent-ready area: ui-server priority: p2 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
schlessera/brain-kit#2758 ·
Maintainers usually reply within 1 day
-
agent-ready area: ci area: ui-react priority: p2 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
schlessera/brain-kit#2615 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-ready area: ci area: docs type: docs
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
schlessera/brain-kit#2612 ·
Maintainers usually reply within 1 day
All issues in schlessera/brain-kit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Merit-Systems/x402scan#1312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Native Web
Difficulty 1/5 Under an hour Newbie friendliness 80/100
digitalfabrik/integreat-app#4517 ·
Maintainers usually reply within 2 days
-
TLS guide repeats certs/ in the certificate directoryPossibly taken @maheshrijal claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
prometheus/docs#3156 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
medusajs/dtc-starter#90 ·
Maintainers usually reply within 1 day