AgentScan: Move label map to agent-san parameters

[huang-julien]

Closes #

What I did

UPdate agent scan action and move the label rename to agent scan for mixed and automated signal.
Agent-scan doesn't label organic account, so we need to keep the script to label agen-scan: human

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

Needs to be merged prior to testing due to the nature of the action.

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>

Summary by CodeRabbit

• Chores
  • Updated CI workflow to extend PR classification label mappings used by automated scanning.
  • Adjusted labeling behavior so automated "agent-scan:" tags are applied only for organic classifications; removed the previous unconditional community-flagged labeling.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c664c5f4-52d5-4471-ad2c-1e8a2332b45f

📥 Commits

Reviewing files that changed from the base of the PR and between ada6fc1 and 2b96e0f.

📒 Files selected for processing (1)

• .github/workflows/agent-scan.yml

---

📝 Walkthrough

Walkthrough

The PR repins the AgentScan action with new label mapping inputs and updates the labeling script to only add the computed agent-scan:<label> label when classification === 'organic' (removing prior community-flagged handling).

Changes

Agent-scan classification labeling

Layer / File(s)	Summary
Workflow action configuration .github/workflows/agent-scan.yml	The AgentScan GitHub Action is repinned to a new commit and now includes label-* inputs mapping community-flagged, mixed, and automated classifications to specific PR labels.
Script label application logic .github/scripts/agent-scan-label-pr.mjs	The script removes the community-flagged input and guards the octokit.rest.issues.addLabels call so it only runs when classification === 'organic', adding the computed agent-scan:<...> label in that case.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• storybookjs/storybook#34293: Introduced earlier AgentScan wiring and labeling script that this PR modifies.
• storybookjs/storybook#34759: Also adjusts AgentScan CI/labeling flow and touches related workflow/script configuration.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}