[Blog] Add post on permission key migration and PermissionShield integration - #2850

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@collections/_posts/2026/08/02/2026-08-02-refactoring-authorization-at-scale-permission-key-migration.md`:
- Line 332: Update the author metadata sentence beginning “Rishi Raj is” to
hyphenate the compound modifier as “open-source contributor.”
- Around line 143-153: Update the before-and-after example so both snippets use
the same corresponding workspace edit permission: align the CAN check in the
“Before” snippet with Keys.WorkspaceManagementEditEnvironment used by the
“After” snippet, preserving the migration comparison.
- Around line 287-296: Declare and assign the popup button element to btn using
the existing screen.getByTestId lookup before asserting or calling
user.click(btn) in the “respects the permissionKey prop” test.
- Around line 250-267: Update the pipeline diagram’s opening code fence in the
authorization documentation to specify the text language, changing the bare
fence to a text-labeled fence while leaving the diagram content unchanged.
- Around line 122-126: Update the userName construction in permissionUserContext
to filter out missing firstName and lastName values before joining them, then
fall back to loggedInUser?.email when no profile name is present; keep the
existing orgName, roleNames, and memo dependencies unchanged.
- Around line 113-115: Revise the compile-time validation claim to state that
TypeScript verifies only the existence and shape of each Keys.* reference, not
the correctness of manually mapped permission IDs, actions, or scopes. Do not
claim full mapping validation unless an executable check against generated
permission metadata is added.
- Around line 246-271: Update the “Pipeline, End-to-End” section to reflect that
the workflow commits only server/permissions/keys.csv, while schema publication
and the versioned `@meshery/schemas` dependency update occur separately before the
UI rebuild consumes new permission keys. Either document those release and
rebuild steps explicitly or revise the claims about immediate imports and
TypeScript compile errors to match the actual propagation process.