Add source project key to migration reports

[okorach-sonar]

Summary

• Adds the source project key beneath the project name in the Projects section's Name column (PDF + Markdown), styled like the target project key already is in the Details column, with a line break between name and key.
• Applies to both the actual (migration_summary) and predictive (predictive_migration_summary) reports, since both share the same rendering pipeline.
• Threads the source key through every bucket a project can land in: Succeeded, Skipped, Failed (via a name-based lookup against generateProjectMappings, since the analysis-report ledger backing Failed rows has no key field), and Partial/NearPerfect (carried over from the matching Succeeded/config-failure entry).

Test plan

• go build ./..., go vet ./..., go test ./... all pass
• New unit tests: EntityItem.SourceKey propagation across Succeeded/Skipped/Failed/Partial buckets, drawNameCell PDF rendering (bold/regular font split, border pattern parity with drawWrappedCell), and Markdown Name-cell rendering (Name<br>**KEY**)
• Manually rendered a sample PDF and Markdown report and visually confirmed the key renders correctly under the name for every outcome bucket, with non-Projects sections unaffected

Fixes #448

🤖 Generated with Claude Code

[gitar-bot]

💡 Edge Case: Failed source-key lookup collides on duplicate project names

attachFailedSourceKeys builds keyByName keyed solely on the project name (def.NameField) and then assigns items[i].SourceKey by name match. Unlike the Succeeded/Skipped paths (which read the source key directly from the same record), Failed rows are matched purely by name. Project names are not guaranteed unique — the same name can exist across different organizations, or even be reused — so the map silently overwrites earlier entries (last-write-wins). When two projects share a name but have different source keys, a failed row can be annotated with the wrong source key, which is misleading in a migration audit report. Consider disambiguating the lookup by including the organization (the analysis ReportRow carries Organization, and generateProjectMappings rows carry sonarcloud_org_key/sonarqube_org_key), or otherwise handling the collision case rather than blindly overwriting.

Key the lookup by organization + name so projects that share a name across organizations are not conflated.:

keyByName := make(map[string]string, len(mapped))
for _, item := range mapped {
	name := jsonStr(item, def.NameField)
	if name == "" {
		continue
	}
	org := jsonStr(item, "sonarcloud_org_key")
	keyByName[org+"\x00"+name] = jsonStr(item, def.SourceKeyField)
}
for i := range items {
	if key, ok := keyByName[items[i].Organization+"\x00"+items[i].Name]; ok {
		items[i].SourceKey = key
	}
}

_{Was this helpful? React with 👍 / 👎}

[gitar-bot]

Code Review 👍 Approved with suggestions 0 resolved / 1 findings

Migration reports now display source project keys beneath project names for improved traceability across all outcome buckets. Note that the lookup mechanism for failed migrations relies on project names and may encounter collisions if duplicate names exist.

💡 Edge Case: Failed source-key lookup collides on duplicate project names

📄 go/internal/report/summary/collect.go:822-836

attachFailedSourceKeys builds keyByName keyed solely on the project name (def.NameField) and then assigns items[i].SourceKey by name match. Unlike the Succeeded/Skipped paths (which read the source key directly from the same record), Failed rows are matched purely by name. Project names are not guaranteed unique — the same name can exist across different organizations, or even be reused — so the map silently overwrites earlier entries (last-write-wins). When two projects share a name but have different source keys, a failed row can be annotated with the wrong source key, which is misleading in a migration audit report. Consider disambiguating the lookup by including the organization (the analysis ReportRow carries Organization, and generateProjectMappings rows carry sonarcloud_org_key/sonarqube_org_key), or otherwise handling the collision case rather than blindly overwriting.

Key the lookup by organization + name so projects that share a name across organizations are not conflated.

keyByName := make(map[string]string, len(mapped))
for _, item := range mapped {
	name := jsonStr(item, def.NameField)
	if name == "" {
		continue
	}
	org := jsonStr(item, "sonarcloud_org_key")
	keyByName[org+"\x00"+name] = jsonStr(item, def.SourceKeyField)
}
for i := range items {
	if key, ok := keyByName[items[i].Organization+"\x00"+items[i].Name]; ok {
		items[i].SourceKey = key
	}
}

🤖 Prompt for agents

Code Review: Migration reports now display source project keys beneath project names for improved traceability across all outcome buckets. Note that the lookup mechanism for failed migrations relies on project names and may encounter collisions if duplicate names exist.

1. 💡 Edge Case: Failed source-key lookup collides on duplicate project names
   Files: go/internal/report/summary/collect.go:822-836

   `attachFailedSourceKeys` builds `keyByName` keyed solely on the project name (`def.NameField`) and then assigns `items[i].SourceKey` by name match. Unlike the Succeeded/Skipped paths (which read the source key directly from the same record), Failed rows are matched purely by name. Project names are not guaranteed unique — the same name can exist across different organizations, or even be reused — so the map silently overwrites earlier entries (last-write-wins). When two projects share a name but have different source keys, a failed row can be annotated with the wrong source key, which is misleading in a migration audit report. Consider disambiguating the lookup by including the organization (the analysis `ReportRow` carries `Organization`, and `generateProjectMappings` rows carry `sonarcloud_org_key`/`sonarqube_org_key`), or otherwise handling the collision case rather than blindly overwriting.

   Fix (Key the lookup by organization + name so projects that share a name across organizations are not conflated.):
   keyByName := make(map[string]string, len(mapped))
   for _, item := range mapped {
   	name := jsonStr(item, def.NameField)
   	if name == "" {
   		continue
   	}
   	org := jsonStr(item, "sonarcloud_org_key")
   	keyByName[org+"\x00"+name] = jsonStr(item, def.SourceKeyField)
   }
   for i := range items {
   	if key, ok := keyByName[items[i].Organization+"\x00"+items[i].Name]; ok {
   		items[i].SourceKey = key
   	}
   }

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
89.2% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud