suite-layout-consultant
Skill1k starsChanged 15 days agoApache-2.0View on GitHub
Decide where new or changed integration-v2 runners, features and overlays belong in the grouped 4-lane CI suite layout, from measured runtime. Measures a runner's isolated runtime, models block length (boot + longest lane) and the per-group 4-queue packing, and recommends the cheapest placement: extend an existing feature/runner, join a compatible block, merge an orthogonal overlay, split an oversized runner/feature, and only as a last resort a new block. Mandatory for test-coverage work that adds or grows runners, features, blocks or overlays; also use to audit or rebalance the suite layout.
Trending
Steady talk.about the whole repository
Who's talking about wso2/product-apim
- Stack Overflow“WSO2APIM v4.2: WebSocket connection timed out by GLOBAL_TIMEOUT config”Stack Overflow · Jul 6, 2023 · 2 votes
- Stack Overflow“how to apply bug fixes on open source wso2 API Manager 4.0.0 and wso2 Micro Integrator 1.2.0”Stack Overflow · Jan 20, 2023 · 2 votes
- wso2/carbon-apimgt“Fix service catalog and publisher permissions to required fields”GitHub · Apr 17, 2021 · 2 reactions
- wso2/carbon-apimgt“Update onboarding pages”GitHub · Apr 9, 2021 · 2 reactions
- wso2/carbon-apimgt“Adding scope role mapping to admin portal”GitHub · Jan 23, 2020 · 2 reactions
The biggest 5 of 76 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 76
Talked about on GitHub and Stack Overflow (76 times).
On GitHub · 50
- Apr 17, 2021Fix service catalog and publisher permissions to required fields — wso2/carbon-apimgt2 reactions
- Apr 9, 2021Update onboarding pages — wso2/carbon-apimgt2 reactions · 1 comment
- Jan 23, 2020Adding scope role mapping to admin portal — wso2/carbon-apimgt2 reactions
- Aug 29, 2019Improve configuration page user experience — wso2/carbon-apimgt2 reactions · 4 comments
- Oct 17, 2024http_access_log.enabled = false does not really disable the http access — wso2/api-manager1 reaction
45 more on GitHub
- Jun 15, 2021Clear details when configuring the DCR via APIM with WSO2 IS as KM — wso2/docs-apim1 reaction · 2 comments
- Aug 6, 2020[3.1.0] Wrong `user_store` type configurations for JDBC User Store — wso2/docs-apim1 reaction
- Feb 27, 2020Fix swagger ui payload not getting sent error in POST request — wso2/carbon-apimgt1 reaction
- Feb 12, 2020Java (Maven): Actually fix the use of insecure protocol to download/upload artifacts — github/securitylab1 reaction · 10 comments
- Oct 8, 2019JWT Token Revocation [Upgrade Needed] — wso2/product-microgateway1 reaction
- Oct 2, 2019Add empty value validation to rest API required fields — wso2/carbon-apimgt1 reaction · 1 comment
- Sep 12, 2019Fixing login loop when no permission for publisher — wso2/carbon-apimgt1 reaction
- Nov 9, 2026Fail over to fallback models on timeouts and connection errors — wso2/carbon-apimgt0 reactions · 20 comments
- Oct 13, 2026Move/Remove unused sample codes from product-apim repository — wso2/api-manager0 reactions
- Oct 12, 2026Show total complexity of the selected query in the GraphQL try-out Query Complexity Analyzer — wso2/apim-apps0 reactions · 2 comments
- Sep 21, 2026Document per-policy compliance affecting severities — wso2/docs-apim0 reactions · 11 comments
- Sep 14, 2026[4.6.0] Document severity-based governance compliance — wso2/docs-apim0 reactions · 1 comment
- Aug 21, 2026[4.11.x] Return a 404 response for invoking APIs with incorrect tenant domains — wso2/carbon-kernel0 reactions · 3 comments
- Aug 19, 2026Remove warning for path parameters in WebSub topic operations — wso2/apim-apps0 reactions · 2 comments
- Aug 18, 2026Stop Info Severity Rule Violations from Failing Governance Compliance — wso2/carbon-apimgt0 reactions · 1 comment
- Aug 5, 2026[4.11.x] Port tomcat template configs for web portal securing — wso2/carbon-kernel0 reactions · 1 comment
- Jul 1, 2026Fix UI issues in admin and devportal for custom keymanager configs — wso2/apim-apps0 reactions · 4 comments
- May 12, 2026Add test case for backend throughput throttling validation — KenathKapilarathna/product-apim0 reactions
- Sep 3, 2025Issue — ranuka-laksika/docs-apim0 reactions · 1 comment
- Sep 2, 2025Issue — ranuka-laksika/docs-apim0 reactions
- Aug 27, 2025Need to replace Slack with Discord in README.md — wso2/docs-apim0 reactions
- Jan 23, 2024Tenant Support for Integration Tests Added for Gateway Policy Feature — wso2/api-manager0 reactions
- Dec 20, 2023Unable to build docker image of Api Manager 4.1 — wso2/api-manager0 reactions · 3 comments
- Mar 9, 2023[mTLS] Wait approximately 10 minutes to allow the cert to be loaded into memory in mTLS authentication — wso2/docs-apim0 reactions
- Feb 17, 2023[Improvement]: Support proxy support in data publishing with Choreo analytics — wso2/api-manager0 reactions
- Sep 20, 2022Missing link in documentation version 3.1 — wso2/docs-apim0 reactions
- Jul 5, 2022Implement Integration test for Websocket transport to validate closed backend connections — wso2/api-manager0 reactions
- Apr 15, 2022Improve UI/UX related to Call Interceptor Service Policy by supporting an `Enum Array` input type — wso2/api-manager0 reactions
- Nov 19, 2021Defined allowed cipher for WSS endpoints in APIM 3.2.0/APIM 4.0.0 — wso2/docs-apim0 reactions · 1 comment
- Jun 23, 2021Create template for docs-ei repo — wso2/docs-apim0 reactions · 1 comment
- Apr 9, 2021Petstore swagger URL wrong — wso2/docs-apim0 reactions
- Apr 8, 2021Need to update the docs: Role Permissions -> Scope Assignment — wso2/docs-apim0 reactions
- Apr 5, 2021Add information to change bindaddress when ssl reload happens in windows — wso2/docs-apim0 reactions
- Apr 2, 2021Fix API Property based filtering — wso2/carbon-registry0 reactions · 1 comment
- Mar 29, 2021Need update docs related to customizing Store/GW urls for tenants — wso2/docs-apim0 reactions · 1 comment
- Mar 15, 2021Include --optimize when starting Key Manager profile — wso2/docs-apim0 reactions
- Feb 22, 2021Update config-catalog with Registry Handler configurations — wso2/docs-apim0 reactions
- Feb 4, 2021Add more information to Enabling Self Signup page for tenants — wso2/docs-apim0 reactions
- Dec 14, 2020Fix invalid url error message — wso2/carbon-kernel0 reactions
- Nov 18, 2020Details on provisioning handler implementation to keep all system roles without being deleted during the provisioning process — wso2/docs-apim0 reactions · 1 comment
- Apr 6, 2020Add role based validation on JWT grant configuration guide — wso2/docs-apim0 reactions
- Jan 9, 2020Set publisher AuthManager ServerURL to localhost — wso2/kubernetes-apim0 reactions
- Nov 26, 2019Fixing issue #6673 — wso2/carbon-apimgt0 reactions · 1 comment
- Nov 20, 2019Fixes documents issues — wso2/carbon-apimgt0 reactions · 1 comment
- Nov 18, 2019Fix issue #6690 — wso2/carbon-apimgt0 reactions · 1 comment
On Stack Overflow · 26
- Jul 6, 2023WSO2APIM v4.2: WebSocket connection timed out by GLOBAL_TIMEOUT config2 votes
- Jan 20, 2023how to apply bug fixes on open source wso2 API Manager 4.0.0 and wso2 Micro Integrator 1.2.02 votes · 2 answers
- Oct 16, 2018How to build/package wso2 api manager Identity Server as Key Manager2 votes
- May 25, 2023Enable AI-based Recommendations for the WSO2 Developer Portal1 vote
- May 25, 2023WSO2 APIM New Install Won't Call APIs - APILoggerManager Errors1 vote
21 more on Stack Overflow
- Nov 8, 2022WSO2 Api Manager 4.1.0 logging continuously Message dispatched to the main sequence. Invalid URL., RESOURCE = / HEALTH CHECK URL = /1 vote
- Oct 6, 2021Problems with authentication login in Pizza Shack WSO2 API Manager1 vote
- May 10, 2021Wso2 APIManager 3.2.0 How can download Analytics for it?1 vote
- Aug 25, 2020How to enable Jaeger opentracing in WSO2-APIM 3.1.0?1 vote
- Aug 12, 2020Wso2 carbon/apimgt open source code download1 vote
- Jun 30, 2020WSO2 API update REST API throwing exception1 vote
- Jun 28, 2020WSO2 Api Manager - Sandbox/Production keys1 vote
- Mar 18, 2020When clicking on the Forgot password link of a service provider oauth2 login, the user is redirected to the Carbon login page1 vote · 1 answer
- Dec 18, 2019WSO2 APIM 3.0.0: Unable to generate access token from devportal1 vote
- Nov 13, 2019SOAP API pass through in WSO2 API manager v3.0.01 vote
- Mar 13, 2019WSO2 API Manager: Creating SOAP or websocket API changes existing APIs types1 vote · 1 answer
- Jul 16, 2018wso2am 2.2.0 publisher in HA setup1 vote
- Jun 19, 2018WSO2 APIM Application Registration urn:approve action not found1 vote · 1 answer
- Nov 21, 2016monetisation labels won`t work as espected for AM 2.01 vote
- Jun 13, 2023WSO2: What are the differences between some of WSO2's repositories?0 votes · 1 answer
- Jan 28, 2023Extending the group ID extractor in WSO2 APIM for Custom User Claim0 votes
- Oct 8, 2020Issue in SOAP API publishing in wso2 3.0.00 votes
- Mar 26, 2020WSO2 APIM 3.0 Configuration proxy problem0 votes
- Feb 27, 2020java.lang.ClassNotFoundException: com.fasterxml.jackson.databind.ObjectMapper cannot be found by org.wso2.carbon.apimgt.keymgt_6.4.500 votes · 1 answer
- Feb 14, 2018WSO2 Api Manager - Generating REST APIs from SOAP0 votes
- Feb 12, 2018Deploying WSO2 API Manager .war on tomcat0 votes · 1 answer
In this repository3 other files it gives its agents.
- block-log-auditSkill
- parity-checkerSkill
- test-coverageSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Every test change can erode that: a new block costs a whole container boot (~115–170 s, more with an IS) before it runs one scenario.
- Distinctive: line 51
Consolidation must not change what a test proves: Before co-locating, read each block's suite comment and runner javadoc, verify the claim …
- Distinctive: line 58
Verify the placement at runtime: Run the affected block(s) after the change.
- Distinctive: line 84
When asked to optimise the whole suite rather than place one change, the scope is every block: work from the hotspots the metrics show …
- Very specific: line 103
If the suite at the change's commit declares no group (a branch from before the group split), its CI ran each topology as one job: model it …
- Very specific: line 105
Run scripts/suite_timings.py <testng-results.xml | job log> <suite xml> --features <out dir>/features: it prints the deterministic metrics …
- Very specific: line 113
Run a focused suite holding the candidate block (or a temporary block with only the new runner, thread-count="1", same overlay and …
- Very specific: line 168
Contention: Before and during every timed run, check what else runs on the Docker host (docker ps, other Maven processes).
- Very specific: line 174
Use references/report-template.md exactly: the verdict table, the tool's metrics pasted verbatim (baseline and the recommended layout's …
- Distinctive: line 185
no new block is added without the measured case and lead approval.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Integration-V2 Suite Layout Consultant
The product suite exists in two topologies with one shared block and runner layout: testng-v2.xml (one all-in-one
APIM per block) and testng-v2_distributed.xml (control plane, traffic manager and gateway per block), kept aligned by
docs/devs/suite_alignment.py. Every block declares a group; CI runs each topology as one job per group
(-Dapim.v2.test.groups), all jobs side by side, each on a 4-CPU / 16 GB GitHub runner running 4 of its group's blocks
at a time (<suite parallel="tests" thread-count="4">). Each block boots its own containers (and any IS/Squid/Solace it
needs), runs its runners on thread-count lanes, and tears down. Wall time is therefore set by how each group's blocks
pack into its 4 queues, and the suite ends with its longest group. Consolidating overlays, merging blocks, splitting by
measured time, setting thread-count per workload and splitting the suite into two groups took the all-in-one suite
from about 2 h 30 min to about 1 h 37 min per run (PR #14336: 37 blocks, 36,620 s of block time, groups of 70 and
97 min).
Every test change can erode that: a new block costs a whole container boot (~115–170 s, more with an IS) before it runs
one scenario; a long runner appended to a thread-count="1" block stretches that block for everyone; a feature that
keeps growing turns its runner into the suite's critical path. This skill makes placement a measured decision, not a
default.
Rules you must obey when changing test layout: all-in-one-apim/modules/integration-v2/tests-integration/cucumber-tests/CLAUDE.md
(§10 runner grouping and lexicographic feature order, §13 overlays, thread-count, CPU caps).
Operating principles
- Measure, don't guess. A placement decision cites the runner's measured isolated runtime and the current block
lengths, from runs (
scripts/suite_timings.py). Spans measured under concurrency include contention; use them for the current layout, use isolated runs for the new work. - Preference order (cheapest first). (1) extend an existing feature in an existing runner; (2) a new runner in an existing block whose overlay and behaviour already suit it; (3) merge a small, orthogonal overlay into a compatible block (how WsProxy and NetworkAccessControl were absorbed); (4) split an oversized runner or feature across lanes or blocks; (5) a new block — only when no compatible block exists, with the measured case and lead approval.
- Any block can be the host, not only blocks of the same feature area. A block that lacks a component the runner needs (an external IS, Squid, Solace, a platform gateway) can still host it: the block gains that component and its overlay, and the suite saves the runner's own block boot. Evaluate every block, and prefer hosts that are small (one to three runners), boot-dominated (short runners, so the addition does not create a new long block), not sensitive to what the addition changes (an overlay's tenant, session, URL or key-manager settings apply to every runner of the host), and free of server restarts. A large block is a poor host even when compatible: the added component holds its memory and CPU for the whole block while most runners never use it, and every runner is exposed to its overlay. Compare each candidate's saving (one boot minus the added component's start-up) with merging into the block that already has the component, and verify the chosen host at runtime.
- Consolidation must not change what a test proves. Before co-locating, read each block's suite comment and runner javadoc, verify the claim behind any "keep separate" note (comments can be stale), list every block that runs a shared feature, and check that neither overlay changes the other's behaviour. A test that goes green because its config silently changed is worse than a slow one.
- The budget is the suite's, not the block's. A change is acceptable when the modelled suite time and packing stay within budget (no queue over ~3,600 s, efficiency not degraded) — a block that is "only" 10 minutes longer can push the whole suite past the target.
- Verify the placement at runtime. Run the affected block(s) after the change; for a new or reshaped block, run it concurrently with the other heavy blocks (a 4-block focused suite) to confirm stability under contention.
Procedure
0. Scope the change under review
Given a pull request (URL or number), a branch or a diff: list every runner, feature, block, overlay and
serverFilesToCopy it adds or changes, and every block whose runner list or thread-count it touches (diff the suite
file against the base). These are what you evaluate. If it changes tests-common/testcontainers/src/main/resources/
nodeapps, every run you make needs a backend image built from that change (mvn test does not rebuild images): build
a private tag from the worktree's nodeapps and pass -Dnode.docker.image.name=<tag>; remove it afterwards. If it
changes the product itself (a dependency version in a product pom.xml, or any module a distribution is built from),
the existing APIM images do not contain the change: build them from the worktree natively (never reuse CI's amd64
images) the way CI's v2-build-images job does, under private tags so the shared tags other checkouts use stay intact:
(1) mvn clean install -Dmaven.test.skip=true -DskipBenchMarkTest=true -DskipRestartTests=true from the repository
root (its reactor includes api-control-plane, gateway and traffic-manager; -f all-in-one-apim/pom.xml leaves
them out, and the image step then silently packages stale component zips from an earlier build); (2) in
all-in-one-apim/modules/integration-v2, mvn install -Pinclude-distributed-images -pl tests-integration/cucumber-tests
-am -DskipTests. Pass the same -Dapim.docker.image.name, -Ddistributed.apim.{cp,tm,gateway}.image.name and
-Dnode.docker.image.name private tags to both steps and to every run. A distributed run reads the image defaults the
image step stages under tests-common/testcontainers/target/distributed-apim/defaults and finds them itself; a
checkout that did not run the image step needs -Ddistributed.apim.defaults.directory pointing at a built
checkout's copy (a focused mvn test does not stage them). A full build needs about 30 GB free on the host: check
df -h / before and during it and stop below 3 GB (a full host disk corrupts the Colima VM). Remove the tags
afterwards. Work on a local checkout only: never push to, comment on, review or otherwise act on the pull request.
When asked to optimise the whole suite rather than place one change, the scope is every block: work from the hotspots the metrics show (critical-path and boot-dominated blocks, tail runners, imbalanced lanes, multi-block registrations, the file-order versus longest-first gap) and propose changes in the preference order below, each modelled on its own.
1. Baseline the current layout
Take the baseline from an existing full run, never from a new full local run. In order of preference:
- A pull request URL/number or a workflow run id (preferred):
scripts/fetch_ci_timings.sh <PR | run id> <out dir> [--topology all-in-one|distributed]downloads the topology'stestng-results.xml(block and runner timings under real CI conditions), its suite file at the run's commit, the features and the job log. It finds the topology's group jobs from the run and merges all of their reports (and logs), failing rather than returning only some groups;suite_timings.pyseparates them again by each block'sgroup. Choose the topology from the change: a distributed-only block, overlay or component parameter (.cp/.tm/.gateway) is decided ondistributed; everything else onall-in-onefirst. A block or group change applies to both suites (they stay aligned), so check the decision against the other topology's baseline too: the same block can be the long pole in one and not the other. - A raw CI job log (when the reports artefact has expired, ~90 days): block-level timings only, from the
BlockLifecycleListenerlines; runner times then come from your isolated runs (step 2). - A local
testng-results.xmlfrom a full local run (last resort, only when no CI data exists): state in the report that it reflects local conditions (different CPU, concurrency and platform from CI). If the suite at the change's commit declares nogroup(a branch from before the group split), its CI ran each topology as one job: model it as one group, say so, and state where the change would belong once rebased onto the grouped layout. Runscripts/suite_timings.py <testng-results.xml | job log> <suite xml> --features <out dir>/features: it prints the deterministic metrics the report pastes (run summary, blocks, top runners, top features, slowest scenarios, multi-block runners, layout model per group, group balance and longest-first regrouping).--group <name>limits it to one group's job. Read each candidate block's suite comment,thread-count, overlays, parameters (apimCpuLimit,initBackend,bootExternalIdentityServer,lifecycleLock, ordering notes such as "keep X last").
2. Measure the new/changed work in isolation
Run a focused suite holding the candidate block (or a temporary block with only the new runner, thread-count="1",
same overlay and parameters) and read the runner's span from its testng-results.xml. Report the isolated runtime per
runner and per feature file (the Cucumber timestamps of the first and last scenario give per-feature time). If a feature
or runner is growing, compare with its previous span.
3. Model the candidates
For each placement option, write a what-if file (<block> <runner> <seconds>, <block> thread-count <n>,
<block> remove <runner>, <block> drop, <block> position <n>, <block> group <name>; a new block name pays the
boot cost) and run suite_timings.py ... --what-if <file>. The modelled suite time is the longest group's file-order
dispatch, which is what TestNG runs in each CI job (it matched CI within 0.3%). The longest-first figure beside it is
a heuristic candidate order (greedy longest-first packing), not a guaranteed optimum and sometimes longer than the file
order: propose a reorder only when its modelled time is actually lower, and model any other order you consider with
position lines. Any block a change adds or lengthens must be placed in the group and file position where the model
says it costs least. Longest-first regrouping is likewise a heuristic: a lower figure suggests a group rebalance to
model with group lines (and to apply in both suites). Compare modelled suite time, the fullest queue and packing
efficiency. A measured block span includes any lifecycle-lock wait; the wait occupies a slot, so never subtract it from
the span when modelling. Removing a lock holder takes its whole span out of its group. Regrouping moves that span: model
both groups (group lines) and compare both groups' modelled times. Measured spans do not show the lock waits
regrouping changes: a block that waited on the moved holder no longer waits in the source group, and the moved block
can wait behind another holder in the target group, so adjust those spans by hand and state the adjustment. See
references/layout-model.md for the model and its limits, and references/consolidation-playbook.md /
references/splitting-playbook.md for what makes an option valid.
4. Check compatibility of the chosen option
Overlay orthogonality (TOML tables and keys, j2 templates, arrays that replace defaults), server-global state and
restarts (thread-count must be 1 if anything restarts or flips global config), workload type (CPU-bound runners at low
thread-count, wait-bound runners can share lanes), lifecycle locks and fixed aliases (browser blocks, external-IS
notification alias), ordering constraints, shared feature files run by other blocks, tenant/actor provisioning the
block needs (initTenantUsers, initSecondaryUserStore, emailUserMode).
Lifecycle locks (lifecycleLock, e.g. browser-sso for blocks that drive the browser against an external IS) are a
JVM-wide semaphore that BlockLifecycleListener acquires at block start on the block's own TestNG thread. A block
waiting for the lock holds one of its group's 4 slots idle until the holder finishes; that slot runs nothing else.
Blocks sharing a lock in the same group must therefore be far apart in file order: the distance lets the first usually
finish before the next is dispatched, which reduces idle lock waiting but does not guarantee it, so model the placement
(§3) to confirm; blocks in different groups run in separate CI jobs and JVMs and never wait on each other. Prefer
placing a new lock-holding block in a group without another holder.
5. Apply and verify
Make the change in the suite (and overlays/runners/feature splits), regenerate the coverage tree if features or runners
changed (render_coverage_tree.py, require invalid: 0 and not-executed: 0), run the affected block(s), then a
4-block focused run with the heaviest neighbours. Re-run suite_timings.py on the result.
Running blocks locally
Runs are focused suites of complete blocks, from all-in-one-apim/modules/integration-v2:
mvn -o -B test -pl tests-integration/cucumber-tests -am -Dsurefire.suite.xml=<suite> (-am is required: without it
stale upstream modules are used; test, never install, so the product image is not rebuilt, except for the
private-tag image build in §0). On macOS with Colima
export first: DOCKER_HOST=unix://$HOME/.colima/default/docker.sock,
TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=/var/run/docker.sock, TESTCONTAINERS_HOST_OVERRIDE=localhost,
TESTCONTAINERS_RYUK_DISABLED=true. A fresh worktree lacks the generated IS trust material: copy
tests-common/testcontainers/target/is7 from a built checkout before running external-IS blocks. It also lacks the
staged distributed image defaults: for distributed blocks pass -Ddistributed.apim.defaults.directory pointing at a
built checkout's tests-common/testcontainers/target/distributed-apim/defaults.
Contention. Before and during every timed run, check what else runs on the Docker host (docker ps, other Maven
processes). A span measured while another block or agent ran is contaminated: label it so in the report, never use it
as an isolated runtime, and re-measure after the host is quiet if the decision depends on it. Never stop containers or
processes you did not start. Local spans (macOS, Colima) are not CI spans: compare local with local, and CI with CI.
6. Report
Use references/report-template.md exactly: the verdict table, the tool's metrics pasted verbatim (baseline and the
recommended layout's what-if comparison), measured runtimes, hotspots, one proposals table (each with its own
modelled before/after, validity and verification status), compatibility evidence, runtime verification and residual
risk. For long runs keep a status note with the phase and an ETA as a clock time.
Gate criteria (when used by test-coverage)
The layout change is acceptable when:
- the new/changed runners' isolated runtimes are measured and reported;
- the chosen placement is the cheapest valid option in the preference order, or the report shows why cheaper options are invalid (with evidence, not assertion);
- no new block is added without the measured case and lead approval;
- the modelled suite time does not exceed the budget and packing efficiency does not drop materially (state both before/after); no single block exceeds ~3,600 s;
- the affected blocks ran green after the change.
Scope boundaries
One layout question per invocation. Never stage or commit. Delete every temporary focused suite (zz-*.xml) and scratch file
the invocation created before finishing, and confirm with git status --porcelain. Do not run the full suite without the developer's consent;
focused suites are the default. Follow the repository's lock or concurrency convention for Docker and Maven runs.
References
references/layout-model.md— lanes, block length, queue packing, budget, boot and resource costs, model limitsreferences/consolidation-playbook.md— how to merge blocks/overlays safely (WsProxy, NetworkAccessControl examples)references/splitting-playbook.md— splitting runners, features and blocks by time; ordering and fixturesreferences/report-template.md— the consultant reportscripts/fetch_ci_timings.sh— fetch a PR's or run's testng-results.xml, suite file and job log from CI (per topology, every group job merged)scripts/suite_timings.py— measured block/runner timings and the per-group 4-queue model with what-if layouts (also reads a job log for block-level timings)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

