---

This section details on the original issue you should resolve

<issue_title>Inline Rendering of lifelib Cell Documentation in Sphinx</issue_title>
<issue_description>### Background

The directories listed below are located under makedocs/source/libraries and contain .rst files used by the Sphinx documentation generator.

• appliedlife
• basiclife
• savings

Each directory documents a lifelib library, which contains one or more lifelib models.

Each model is documented in a .rst file.
A model may contain a single space or multiple spaces.
If a model contains multiple spaces, each space is documented either:

• in a separate .rst file, or
• within the model’s main documentation file.

---

Models, Spaces, and Cells

Models and spaces are represented by Python modules.
They contain Cells, which are represented by Python functions.

Currently, Sphinx (via the autosummary extension) auto-generates a separate page for each Cell, based on the Cell’s docstring. This significantly increases documentation build time.

---

Goal

Instead of generating separate pages for each Cell, render the Cell docstrings on the same page as the corresponding model or space documentation.

---

Required Changes

To achieve this, apply the following steps:

1. Modify the autosummary directive

In the directories listed above, identify autosummary directives that generate separate pages for Cells and remove the :toctree: and :template: options.

2. Add a “Cells Descriptions” section

At the bottom of the same .rst file:

• Add a section titled “Cells Descriptions”
• For each Cell listed in the autosummary, add an autofunction directive so the Cell documentation is rendered inline.

---

Example

Before

.. autosummary::
   :toctree: ../generated/
   :template: mxbase.rst

   ~age
   ~age_at_entry

After

.. autosummary::

   ~age
   ~age_at_entry

Then, add the following section at the end of the file:

Cells Descriptions
------------------

.. autofunction:: age

.. autofunction:: age_at_entry

</issue_description>

Comments on the Issue (you are @copilot in this section)