mochan-tk / mochan-tk/agentic-dev-kit-for-copilot

retro-candidate: every session carries two IDs (app project session vs CLI tool) and no record rule says which is canonical

Open
#150 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

retro:candidate
Dominant language
Shell
Stars
5
Forks
0
Avg merge
16h 36m
Merged PRs (30d)
15

Description

Occurrence: https://github.com/mochan-tk/agentic-dev-kit-for-copilot/issues/136#issuecomment-5739308277

Every app-managed session has two identifiers: the app project session ID shown in the app, and the CLI/tool session ID that list_sessions_and_chats returns as id and that the session tools accept. Startup, dispatch and teardown records in Epic #119 had to carry both (for example the Task #136 supervisor startup above and the Task #138 dispatch record https://github.com/mochan-tk/agentic-dev-kit-for-copilot/issues/119#issuecomment-5739625579), and the coordinator re-resolved them with get_session each time. The session-orchestration skill does not say which identifier a record must cite.

This issue records the bookkeeping friction only (first occurrence); it does not authorize skill changes.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked occurrence in issue #136 and compare the supervisor startup and dispatch records in Epic #119, including the identifiers from list_sessions_and_chats and get_session. Done would require a decided canonical-record rule, but this issue explicitly records bookkeeping friction only and does not authorize skill changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
developer-experience
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.