* {@code @ParametricNullness E}, which means:
 *
 * <ul>
 *   <li>{@code getElement} on a {@code Multiset.Entry<@NonNull String>} returns {@code @NonNull
 *       String}.
 *   <li>{@code getElement} on a {@code Multiset.Entry<@Nullable String>} returns {@code @Nullable
 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.

										<span class="badge rounded-pill text-bg-secondary float-end">${f:h(countEntry.value)}</span>
								</la:link></li>
						</c:if>
					</c:forEach>
				</ul>
			</c:if>
		</c:forEach>
		<c:forEach var="facetQueryView" items="${fe:facetQueryViewList()}">
			<ul class="list-group mb-2">
				<li class="list-group-item text-uppercase"><la:message key="${facetQueryView.title}" /></li>
				<c:set var="facetFound" value="F"/>

 * <h2>Architecture Overview</h2>
 *
 * <h3>Goals</h3>
 * <ul>
 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.Check} - Analyzes projects and reports needed upgrades</li>
 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.Apply} - Applies upgrades to project files</li>
 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.Help} - Displays usage information</li>
 * </ul>
 *
 * <h3>Upgrade Strategies</h3>

 * supports the following key features:
 *
 * <ul>
 *   <li>Maintains parent-child relationships between requests to track operation nesting</li>
 *   <li>Carries contextual data describing the current request or operation</li>
 *   <li>Supports both internal session operations and client-provided trace information</li>
 * </ul>
 *

 *
 * <p>Methods:</p>
 * <ul>
 *   <li>{@link #expired()}: Handles the expiration of connections by closing expired and idle connections.</li>
 * </ul>
 *
 * <p>Logging:</p>
 * <ul>
 *   <li>Logs a warning if the clientConnectionManager is null.</li>
 *   <li>Logs a warning if an exception occurs during connection monitoring.</li>
 * </ul>
 *
 */

 *   <li><b>Max children per node:</b> 2047 (11-bit count in the bitfield)
 * </ul>
 *
 * <p>As of Jan 2026, the capacity usage is approximately:
 *
 * <ul>
 *   <li>Total nodes: ~16% (10k / 65k)
 *   <li>String pool size: ~79% (52k / 65k)
 *   <li>Max children per node: ~71% (1.5k / 2k)
 * </ul>
 *
 * <p>If any of these limits are exceeded, the definitive solution is to increase the node size from
 * 3 to 4 characters. This would allow:

 * terms</a>):
 *
 * <ul>
 *   <li>directed graphs
 *   <li>undirected graphs
 *   <li>graphs that do/don't allow self-loops
 *   <li>graphs whose nodes/edges are insertion-ordered, sorted, or unordered
 *   <li>graphs whose edges have associated values
 * </ul>
 *
 * <p>{@code ValueGraph}, as a subtype of {@code Graph}, explicitly does not support parallel edges,

 * and context necessary for request processing, including:
 * <ul>
 *   <li>User and system properties for interpolation</li>
 *   <li>Session start time information</li>
 *   <li>Project directory structures</li>
 * </ul>
 *
 * <p>Requests can optionally carry trace information through {@link RequestTrace} to support:
 * <ul>
 *   <li>Debugging and troubleshooting of request flows</li>

     * <ul>
     *   <li>For included dependencies: {@code groupId:artifactId:version[:scope] (details)}</li>
     *   <li>For omitted dependencies: {@code (groupId:artifactId:version[:scope] - details)}</li>
     * </ul>
     * Where details may include:
     * <ul>

										<span class="badge rounded-pill text-bg-secondary float-end">${f:h(countEntry.value)}</span>
								</la:link></li>
						</c:if>
					</c:forEach>
				</ul>
			</c:if>
		</c:forEach>
		<c:forEach var="facetQueryView" items="${fe:facetQueryViewList()}">
			<ul class="list-group mb-2">
				<li class="list-group-item text-uppercase"><la:message key="${facetQueryView.title}" /></li>
				<c:set var="facetFound" value="F"/>