{"version":"2.1.277","anchor":"code-attribution-report-can-be-computed-against-a-different","canonical_anchor":"code-attribution-report-can-be-computed-against-a-different","heading":"Code-attribution report can be computed against a different repo root than the current session","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/code-attribution-report-can-be-computed-against-a-different","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Code-attribution report can be computed against a different repo root than the current session\n\nFixes the claude\/human code-attribution report to use the right repo root when computing contribution splits\n\n**What**\n\nThe code-attribution report, which totals up how much of your code came from Claude versus a human, could get confused about which repository it was reporting on. It now separately resolves the repo root that was actually requested and the repo root the current session is really using, and only re-fetches ignored-file information for each root when they differ. Each file's Human\/Claude split is now looked up using a key that includes which root it belongs to, with a fallback if the root doesn't match.\n\n**Why**\n\nThis prevents the report from mixing up contribution data across different repository roots, so the numbers you see for a given repo actually reflect that repo.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}