Perform code optimization and document cleanup (#1)

## Summary
- add repository-wide quality tooling and verification scaffolding, including CI workflows, pnpm workspace setup, ESLint/Prettier/markdown checks, and generated-output verification helpers
- reorganize skill sources and generation flow by introducing canonical `_source` variants, generator/manifests, reusable helper abstractions, and shared web-automation/browser utilities
- clean up and expand documentation so the root README flows into docs and skill docs, with clearer development, reviewer, installer, and workflow guidance

## Notable changes
- docs flow and consistency cleanup across `README.md`, `docs/README.md`, and related docs
- new scripts for `check`, docs verification, generated-file verification, shell portability, and safe directory replacement
- refactors in Atlassian and web-automation skill runtimes to reduce duplication and centralize reusable code
- changelog, development documentation, and CI surface updates

## Test Plan
- [ ] `pnpm run check`
- [ ] review generated/manifests and skill sync outputs
- [ ] smoke-check docs flow from `README.md` to `docs/README.md` to skill docs

## Notes
- this branch currently includes tracked `skills/web-automation/shared/node_modules` content that should be reviewed carefully as potentially noisy/accidental committed artifacts

Co-authored-by: Stefano Fiorini <stefano.fiorini@firsthorizon.com>
Reviewed-on: #1

docs/INSTALLER.md

@@ -1,6 +1,7 @@
 # Skill Manager Installer
 
-Use the skill manager wizard to install, update/reinstall, or remove skills from this repository for supported local coding clients.
+Use the skill manager wizard to install, update/reinstall, or remove skills from this repository
+for supported local coding clients.
 
 ## Quick Start
 
@@ -58,9 +59,12 @@ Workflow skills require Obra Superpowers:
 
 - `create-plan`: `brainstorming`, `writing-plans`
 - `implement-plan`: `executing-plans`, `using-git-worktrees`, `verification-before-completion`, `finishing-a-development-branch`
-- `do-task`: `brainstorming`, `test-driven-development`, `verification-before-completion`, `finishing-a-development-branch` plus conditional `using-git-worktrees`
+- `do-task`: `brainstorming`, `test-driven-development`, `verification-before-completion`,
+  `finishing-a-development-branch` plus conditional `using-git-worktrees`
 
-When a selected install/update needs Superpowers and none are detected for the target client/scope, the wizard asks whether to install them. It asks for an absolute path to an Obra Superpowers `skills` directory and lets you choose symlink or copy:
+When a selected install/update needs Superpowers and none are detected for the target client/scope,
+the wizard asks whether to install them. It asks for an absolute path to an Obra Superpowers
+`skills` directory and lets you choose symlink or copy:
 
 - symlink is recommended because updates to the source checkout are immediately visible
 - copy is more self-contained but must be updated manually
@@ -69,13 +73,19 @@ The wizard recognizes client-native and plugin-managed Superpowers installs befo
 
 - Codex: `~/.agents/skills/superpowers` or `~/.codex/superpowers/skills`
 - Claude Code: `~/.claude/skills/superpowers` or the enabled `superpowers@claude-plugins-official` plugin cache
-- Cursor: `.cursor/skills/superpowers/skills`, `~/.cursor/skills/superpowers/skills`, or the Cursor public Superpowers plugin cache
+- Cursor: `.cursor/skills/superpowers/skills`, `~/.cursor/skills/superpowers/skills`,
+  or the Cursor public Superpowers plugin cache
 - OpenCode: `~/.agents/skills/superpowers` or `~/.config/opencode/skills/superpowers`
 - Pi: `~/.agents/skills/superpowers`, `~/.pi/agent/skills/superpowers`, or `.pi/skills/superpowers`
 
-When Cursor has no plugin/cache install, the wizard installs Superpowers at `<scope>/superpowers/skills` because Cursor variants expect `superpowers/skills/<skill>/SKILL.md`. Symlinking is still preferred when the source tree is managed locally. Codex and OpenCode can commonly reuse the shared `~/.agents/skills/superpowers` convention documented in [CODEX.md](./CODEX.md) and [OPENCODE.md](./OPENCODE.md).
+When Cursor has no plugin/cache install, the wizard installs Superpowers at
+`<scope>/superpowers/skills` because Cursor variants expect
+`superpowers/skills/<skill>/SKILL.md`. Symlinking is still preferred when the source tree is
+managed locally. Codex and OpenCode can commonly reuse the shared `~/.agents/skills/superpowers`
+convention documented in [CODEX.md](./CODEX.md) and [OPENCODE.md](./OPENCODE.md).
 
-When removing the last repository workflow skill from a client/scope, the wizard asks whether to remove Superpowers for that variant too.
+When removing the last repository workflow skill from a client/scope, the wizard asks whether to
+remove Superpowers for that variant too.
 
 ## Reviewer Runtime Helpers
 
@@ -87,7 +97,9 @@ Workflow skills install/update the reviewer-runtime helper bundle automatically
 
 ## Pi Package Mode
 
-Pi can be managed as a package install or by manual skill copy. Package mode always manages the full Pi bundle; per-skill prompts and `--skill` narrowing are ignored for `packageGlobal` and `packageLocal`.
+Pi can be managed as a package install or by manual skill copy. Package mode always manages the
+full Pi bundle; per-skill prompts and `--skill` narrowing are ignored for `packageGlobal` and
+`packageLocal`.
 
 Package-mode actions:
 
@@ -148,6 +160,8 @@ The final report uses these columns:
 
 Exit code is non-zero if any selected operation fails.
 
-Dangling symlink warnings are surfaced as `warning` rows. For example, if a previously symlinked Superpowers source has moved or been deleted, the final report keeps the operation non-destructive and shows the dangling symlink target in `details` so you can repair or remove it deliberately.
+Dangling symlink warnings are surfaced as `warning` rows. For example, if a previously symlinked
+Superpowers source has moved or been deleted, the final report keeps the operation non-destructive
+and shows the dangling symlink target in `details` so you can repair or remove it deliberately.
 
 See [PI.md](./PI.md) for Pi package layout details and mirror maintenance.