Expand forge-lanes.toml path selectors for agent and crate paths
Intent: Ensure that changes to AGENTS.md, the .agents/ directory, crates/pika-news/, and crates/ph/ trigger the correct CI lanes (pika_followup, notifications, and agent_contracts) instead of silently skipping CI.
Affected files: ci/forge-lanes.toml
@@ -37,6 +37,8 @@ title = "check-pika-followup"
staged_linux_target = "pre-merge-pika-followup"
paths = [
"ci/forge-lanes.toml",
+ "AGENTS.md",
+ ".agents/**",
@@ -78,10 +80,12 @@ paths = [
".github/workflows/pre-merge.yml",
"scripts/pikaci-staged-linux-remote.sh",
"scripts/ci-add-known-host.sh",
+ "crates/pika-news/**",
"crates/pikaci/**",
@@ -78,10 +80,12 @@
+ "crates/ph/**",
"crates/pikahut/**",
@@ -101,6 +105,8 @@ title = "check-agent-contracts"
staged_linux_target = "pre-merge-agent-contracts"
paths = [
"ci/forge-lanes.toml",
+ "AGENTS.md",
+ ".agents/**",
@@ -113,10 +119,12 @@
+ "crates/pika-news/**",
"crates/pikaci/**",
+ "crates/ph/**",
Four new glob patterns are added across two lane definitions in ci/forge-lanes.toml:
check-pika-followuplane gainsAGENTS.mdand.agents/**so that agent workflow documentation and skill definitions trigger the followup lane.check-pika-followuplane (notifications section) gainscrates/pika-news/**andcrates/ph/**so forge-web and thephCLI crate are covered.check-agent-contractslane mirrors those same four additions (AGENTS.md,.agents/**,crates/pika-news/**,crates/ph/**).
Without these entries, changes to any of these paths would not trigger the relevant CI lanes, creating a coverage gap where code could land without being validated.