compwron

name	jira-to-linear
description	Import Jira issues into Linear by reading from the Atlassian MCP and creating new issues via the Linear MCP. Use when the user wants to migrate, import, or move issues from Jira to Linear.

Jira to Linear Issue Import

Pre-flight Checks

Before anything else, confirm both MCPs are available:

compwron

Payor Enhanced Workflow Configurations (PR #29154)

Three workflow configurations defined in payorEnhancedWorkflowHelpers.ts:

Flow	payorEnhancedWorkflowFeatures	Supplier can edit	Supplier can attach
nativeNonPayorEnhanced	null	Fillable PDFs only	Depends on updateManualDocumentation permission
ccxExternalPayorEnhanced	All features enabled, external payor rules	Yes (supplierCanEditClinicalInput: true)	Yes (if permission + no warnings)
ihcsNativePayorEnhanced	Native coverage criteria, no medical necessity framing	Yes (supplierCanEditClinicalInput: true)	Yes (if permission + no warnings)

compwron

PR #27746 Review: Documentation Template and Tooling for Domains

What the PR does well

1. Template-driven approach — README_TEMPLATE.md provides a consistent structure, emphasizing public API over internals
2. Packwerk guide — README_PACKWERK.md is a solid standalone reference that centralizes tribal knowledge
3. Worked example — the authorization/README.md shows how the template looks when applied, not just theory
4. Automation via skills — two Cursor skills to regenerate the index and scaffold READMEs, reducing manual upkeep

Where it diverges from ideal

compwron

require_relative Usage Critique — app-workflow

130 occurrences across 102 files

1. Legitimate / Idiomatic (no issues)

• Boot files (config/application.rb, config/environment.rb, bin/rails, bin/rake) — standard Rails convention.
• Gemspec version files (internal_api.gemspec, codebase_vector_store.gemspec) — required before Bundler loads.
• Standalone gem internals (codebase_vector_store/lib/) — manages its own loading outside Rails autoload. The lazy load_models!/load_services! pattern is fine since it deliberately defers loading until a DB connection is ready.
• Gem test_support.rb files (email_validator, archivable, phone_validator, etc.) — expose shared examples to consumers outside Rails autoload.
• Spec shared examples/helpers within the same domain (FHIR controllers, catalog models, qualification specs, cms controllers) — acceptable.

compwron

CTF Priority: Top 20 Files in app-workflow

Ordered by likelihood of finding something exploitable fast.

Tier 1: Auth boundary (where trust is established)

1. config/routes.rb + config/routes/api.rb — map the full attack surface first
2. app/controllers/saml_controller.rb — already has a known CWE-601; SAML is historically rich in bypasses
3. app/controllers/sessions_controller.rb — token login, redirect handling
4. app/controllers/oauth_tokens_controller.rb — Doorkeeper password grant with a TODO about skipping client auth

compwron

Cat Crew YAML Tickets (2025–2026)

Ticket	Status	Date	Summary
WF-38706	Done	2026-02-04	Output of YAML quantity tag is not updated when quantity input is changed
WF-37762	Done	2026-01-05	Create YAML functions for accessing RxQty data by HCPCS
WF-37253	Done	2025-12-04	RX Quantity Tags in YAML
WF-30112	Done	2025-03-12	Check to see how much an "alias" would affect the downstream

Summary

compwron

Disk Usage Analysis — 2026-04-07

494 GB disk, 10.8 GB free (2.2%)

Where the space is going

Area	Size	Notes
Library/Application Support	44 GB	Postgres 11G, Notion 9G, Autodesk 7.7G
Library/Developer	42 GB	CoreSimulator 23G, Xcode 18G

compwron

Dependabot PRs Closed Without Merging — app-workflow

Report compiled 2026-04-07. Covers 50 most recent closed-not-merged dependabot PRs.

"Too old or too scary" (bulk closed by compwron)

• #27937 — sentry group (3 updates)
• #27239 — sidekiq group (2 updates)
• #27842 — webpack 5.102→5.104
• #27806 — aws-sdk-s3, aws-sdk-core, launchdarkly, prawn, rqrcode, savon, pry-byebug, pdf-reader
• #27376 — @csstools/postcss-logical-viewport-units 3.0.3→3.0.4

compwron

name	datadog-controller-search
description	Generate a Datadog Logs Explorer link to search for requests to a specific Rails controller in production. Use when the user asks for a Datadog link, Datadog search, or production traffic for a controller.

Parachute Datadog Controller Search

Generate a Datadog Logs Explorer URL that searches for requests to a specific Rails controller.

When to use

compwron

Clinical Intelligence Datadog Dashboard Plan

Team: clinical-intelligence Existing dashboard: Clinical Intelligence Dashboard (currently minimal) Constraint: No new instrumentation — only existing logs, metrics, and APM spans

Available Data Sources

Source	Key Filter	What's There