cc docs: remove manual links and improve sidebar

Replaced hand-written intra-doc links with automatic doctool linking.
Sidebar now reflects the subsection hierarchy.

Author: bracevac

docs/_docs/reference/experimental/cc-checked-exceptions.md

@@ -86,7 +86,3 @@ To integrate exception and capture checking, only two changes are needed:
  - `CanThrow` is declared as a class extending `Control`, so all references to `CanThrow` instances are tracked.
  - Escape checking is extended to `try` expressions. The result type of a `try` is not allowed to
    capture capabilities defined in the body of the `try`.
-
----
-
-Next: [How to Use the Capture Checker](./cc-how-to-use.md)

docs/_docs/reference/experimental/cc-classes.md

@@ -231,7 +231,3 @@ That variant would not require any capture annotations either.
 To summarize, there are two "sweet spots" of data structure design: strict lists in
 side-effecting or resource-aware code and lazy lists in purely functional code.
 Both are already correctly capture-typed without requiring any explicit annotations. Capture annotations only come into play where the semantics gets more complicated because we deal with delayed effects such as in impure lazy lists or side-effecting iterators over strict lists. This property is probably one of the greatest plus points of our approach to capture checking compared to previous techniques which tend to be more noisy.
-
-----
-
-Next: [Capability Polymorphism](./cc-polymorphism.md)

docs/_docs/reference/experimental/cc-classifiers.md

@@ -107,7 +107,3 @@ def test(io: IO, async: Async, proc: () => Unit) =
     // code accessing `io`, `async`, and `proc` and returning an `Int.
   val _: Try[Int]^{async, proc} = r
 ```
-
----
-
-Next: [Checked exceptions](./cc-checked-exceptions.md)

docs/_docs/reference/experimental/cc-how-to-use.md

@@ -17,7 +17,3 @@ The following options are relevant for capture checking.
  - **-Ycc-debug** Gives more detailed, implementation-oriented information about capture checking, as described in the next section.
 
  The implementation supporting capture checking with these options is currently in branch `cc-experiment` on dotty.epfl.ch.
-
----
-
-To find out more about the internal workings of the capture checker: [Capture Checking Internals](./cc-internals.md)

docs/_docs/reference/experimental/cc-polymorphism.md

@@ -93,7 +93,3 @@ upper bound: `type Cap^ >: {cudaMalloc, cudaFree}`.
 ----
 
 [More Advanced Use Cases](cc-advanced.md)
-
-----
-
-Next: [Scoped Caps](./cc-scoped-caps.md)

docs/_docs/reference/experimental/cc-scoped-caps.md

@@ -118,7 +118,3 @@ def f(ops: List[A => B])
   ...
 ```
 Reach capabilities take the form `x*` where `x` is syntactically a regular capability. If `x: T` then `x*` stands for any capability that appears covariantly in `T` and that is accessed through `x`. The least supertype of this capability is the set of all capabilities appearing covariantly in `T`.
-
----
-
-Next: [Capability Classifiers](./cc-classifiers.md)

docs/_docs/reference/experimental/cc-separation-checking.md

@@ -1 +1,7 @@
+---
+layout: doc-page
+title: "Separation Checking"
+nightlyOf: https://docs.scala-lang.org/scala3/reference/experimental/cc-separation-checking.html
+---
+
 # TODO

docs/_docs/reference/experimental/cc.md

@@ -298,7 +298,3 @@ where `loophole` is defined.
 Looking at object graphs, we observe a monotonicity property: The capture set of an object `x` covers the capture sets of all objects reachable through `x`. This property is reflected in the type system by the following _monotonicity rule_:
 
  - In a class `C` with a field `f`, the capture set `{this}` covers the capture set `{this.f}` as well as the capture set of any application of `this.f` to pure arguments.
-
-----
-
-Next: [Capture Checking of Classes](./cc-classes.md)

docs/sidebar.yml

@@ -162,25 +162,19 @@ subsection:
           - page: reference/experimental/explicit-nulls.md
           - page: reference/experimental/main-annotation.md
           - page: reference/experimental/into.md
-          - page: reference/experimental/cc.md
-          - page: reference/experimental/cc-classes.md
-            hidden: true
-          - page: reference/experimental/cc-polymorphism.md
-            hidden: true
-          - page: reference/experimental/cc-advanced.md
-            hidden: true
-          - page: reference/experimental/cc-scoped-caps.md
-            hidden: true
-          - page: reference/experimental/cc-classifiers.md
-            hidden: true
-          - page: reference/experimental/cc-checked-exceptions.md
-            hidden: true
-          - page: reference/experimental/cc-separation-checking.md
-            hidden: true
-          - page: reference/experimental/cc-how-to-use.md
-            hidden: true
-          - page: reference/experimental/cc-internals.md
-            hidden: true
+          - title: Capture checking
+            index: reference/experimental/cc.md
+            subsection:
+              - page: reference/experimental/cc-classes.md
+              - page: reference/experimental/cc-polymorphism.md
+              - page: reference/experimental/cc-advanced.md
+                hidden: true
+              - page: reference/experimental/cc-scoped-caps.md
+              - page: reference/experimental/cc-classifiers.md
+              - page: reference/experimental/cc-checked-exceptions.md
+              - page: reference/experimental/cc-separation-checking.md
+              - page: reference/experimental/cc-how-to-use.md
+              - page: reference/experimental/cc-internals.md
           - page: reference/experimental/purefuns.md
           - page: reference/experimental/tupled-function.md
           - page: reference/experimental/modularity.md