Kris West

@Yannick-Malins @paulgoldsmith @bingenito Can we get an issue raised to represent the proposed changes, use case etc.? I'm just realizing that there isn't one in place, only the meeting issues....

They weren't matched at one point - I guess we had them change them! I think in an earlier version they created text descriptions of each test and used those....

If the huskey precommit hook isn't working using that shell script, then we can instead configure it in the package.json file by adding: ```json "husky": { "hooks": { "pre-commit": "npx...

> And yes, I've spent quite a while scratching my head over the percentage. I have no idea why this is happening! Have you ended up with multiple tests with...

@Roaders the tests execute serially so its worth identifying which test it gets stuck in. I don't know why you'd be getting less tests total. @robmoffat what do you get...

> This makes a lot of sense, although I think from my perspective it's more in implementation land than standards side. What do the other maintainers think? @robmoffat indeed, it'd...

@rikoe @nkolba The discussion of this proposal at the Standards Working Group was interesting and isn't yet fully represented here (nor are the meeting minutes posted yet, I'm still working...

>It seems like the intended consumer of the traceId is the desktop agent Only in one of the two use cases proposed (and then only to facilitate passing onwards to...

For the tracking use case, I actually wonder whether a single id field is sufficient... Whether the additional metadata goes into the context object or ContextMetadata, it then starts to...

@julianna-ciq we're overdue to update this issue to reflect the more important use cases and to incorporate the proposed changes at meeting #1196 (see minutes posted at bottom of that...