Move docs to separate branch api-serverless-docs

Split out 6 .md files into a separate review path:
- docs/user/00-80-migrate-to-new-runtime-api.md
- docs/user/00-90-runtime-deprecation-schedule.md
- docs/user/technical-reference/05-20-env-variables.md
- docs/user/technical-reference/07-70-function-specification.md
- components/runtimes/{nodejs26,python314}/README_template.md

The eject endpoint will still pick up the updated README templates
once the docs branch is merged.

Author: halamix2

components/runtimes/nodejs26/README_template.md

@@ -1,48 +1,45 @@
 # Ejected Functions Workspace
 
-This folder contains the files you need to test, run, deploy, and productize your business application:
+This folder contains the most important block to test, run, deploy, and productize your business application and consists of the following elements:
 
-* `handler.js` — source code of your business application
-* `server.mjs` — server that loads and runs `handler.js`
-* `package.json` — dependencies for `handler.js` and `server.mjs`
-* `lib/` — internal server modules (tracing, metrics, request timeout, and graceful shutdown)
-* `sdk/` — user-facing SDK module (`require('sdk')`) exposing CloudEvent helpers, tracer, and function metadata getters
-* `resources/` — basic Kubernetes resources for deploying the application on a cluster
-* `Dockerfile` — application image definition
-* `Makefile` — automation scripts
+* `handler.js` - source code of the buisness application
+* `server.mjs` - server source code required to run `handler.js`
+* `package.json` - dependencies file required for the `handler.js` and the `server.mjs` files to run
+* `lib/` - directory containing server SDK (like cloudevents or tracing functionality)
+* `resources/` - directory with basic Kubernetes resources required to deploy the application on a cluster
+* `Dockerfile` - application image definition
+* `Makefile` - basic portion of automations and scripts
 
 ## Scripts and Automations
 
-Use the `Makefile` targets to run the application locally or build and deploy it on a k3d cluster. To see all available targets, run:
+The `Makefile` file is designed to speed up processes such as running an application locally or building or deploying it on a k3d cluster.
 
-```bash
-make help
-```
+Read more about possibilities and functionalites by running the `make help` target.
 
 ### Run Application Locally
 
-> [!NOTE]
-> When you run the application outside the cluster, it cannot reach in-cluster services or read container environment variables. Use this target to test without such dependencies, or mock them and export the environment variables manually.
+> [!NOTE] 
+> Because the application is run outside the cluster, it cannot simply reach in-cluster services and use container envs. It is strongly recommended to use the following target to test the application without such dependencies or mock them and export container envs manually.
 
 ```bash
 export FUNC_NAME=<name>
 export FUNC_RUNTIME=<runtime>
-export SERVICE_NAMESPACE=<namespace>
+export SERVICE_NAMESPACE=<SERVICE_NAMESPACE>
 
 make run
 ```
 
 ### Deploy Application on k3d
 
-To build, import, and deploy the application on a k3d cluster:
+The workspace is designed to easily start working on the productization of a business application extracted from Function. It allows testing it on a k3d cluster by building, importing, and deploying it:
 
 ```bash
 make k3d-deploy
 ```
 
 ### Build and Push Application
 
-To build and push your image to the location specified by `IMG`:
+Build and push your image to the location specified by `IMG`:
 
 ```bash
 make docker-build docker-push IMG=<image>

components/runtimes/python314/README_template.md

@@ -1,47 +1,45 @@
 # Ejected Functions Workspace
 
-This folder contains the files you need to test, run, deploy, and productize your business application:
-
-* `handler.py` — source code of your business application
-* `server.py` — server that loads and runs `handler.py`
-* `requirements.txt` — dependencies for `handler.py` and `server.py`
-* `lib/` — server SDK modules (CloudEvents, tracing, and similar)
-* `resources/` — basic Kubernetes resources for deploying the application on a cluster
-* `Dockerfile` — application image definition
-* `Makefile` — automation scripts
-
+This folder contains the most important block to test, run, deploy, and productize your business application and consists of the following elements:
+
+* `handler.py` - source code of the buisness application
+* `server.py` - server source code required to run `handler.py`
+* `requirements.txt` - dependencies file required for the `handler.py` and the `server.py` files to run
+* `lib/` - directory containing server SDK (like cloudevents or tracing functionality)
+* `resources/` - directory with basic Kubernetes resources required to deploy the application on a cluster
+* `Dockerfile` - application image definition
+* `Makefile` - basic portion of automations and scripts
+   
 ## Scripts and Automations
 
-Use the `Makefile` targets to run the application locally or build and deploy it on a k3d cluster. To see all available targets, run:
+The `Makefile` file is designed to speed up processes such as running an application locally or building or deploying it on a k3d cluster.
 
-```bash
-make help
-```
+Read more about possibilities and functionalites by running the `make help` target.
 
 ### Run Application Locally
 
-> [!NOTE]
-> When you run the application outside the cluster, it cannot reach in-cluster services or read container environment variables. Use this target to test without such dependencies, or mock them and export the environment variables manually.
+> [!NOTE] 
+> Because the application is run outside the cluster, it cannot simply reach in-cluster services and use container envs. It is strongly recommended to use the following target to test the application without such dependencies or mock them and export container envs manually.
 
 ```bash
 export FUNC_NAME=<name>
 export FUNC_RUNTIME=<runtime>
-export SERVICE_NAMESPACE=<namespace>
+export SERVICE_NAMESPACE=<SERVICE_NAMESPACE>
 
 make run
 ```
 
 ### Deploy Application on k3d
 
-To build, import, and deploy the application on a k3d cluster:
+The workspace is designed to easily start working on the productization of a business application extracted from Function. It allows testing it on a k3d cluster by building, importing, and deploying it:
 
 ```bash
 make k3d-deploy
 ```
 
 ### Build and Push Application
 
-To build and push your image to the location specified by `IMG`:
+Build and push your image to the location specified by `IMG`:
 
 ```bash
 make docker-build docker-push IMG=<image>

docs/user/00-80-migrate-to-new-runtime-api.md

@@ -83,18 +83,16 @@ module.exports = {
 
 ```javascript
 // After — sdk functions
-const { getTracer, getFunctionName, getNamespace, getRuntime, getTimeout, getBodySizeLimit } = require('sdk');
-
-module.exports = {
-    main: async function (req, res) {
-        const tracer = getTracer();
-        console.log(getFunctionName());
-        console.log(getNamespace());
-        console.log(getRuntime());
-        console.log(getTimeout());
-        console.log(getBodySizeLimit());
-        res.send('ok');
-    }
+import { getTracer, getFunctionName, getNamespace, getRuntime, getTimeout, getBodySizeLimit } from 'sdk';
+
+export function main(req, res) {
+    const tracer = getTracer();
+    console.log(getFunctionName());
+    console.log(getNamespace());
+    console.log(getRuntime());
+    console.log(getTimeout());
+    console.log(getBodySizeLimit());
+    res.send('ok');
 }
 ```
 
@@ -159,24 +157,22 @@ module.exports = {
 
 ```javascript
 // After — getCloudEvent() returns a standard CloudEvent object
-const { getCloudEvent } = require('sdk');
-
-module.exports = {
-    main: function (req, res) {
-        const ce = getCloudEvent(req);
-        if (ce) {
-            console.log(ce.type);
-            console.log(ce.source);
-            console.log(ce.specversion);
-            console.log(ce.id);
-            console.log(ce.time);
-            console.log(ce.datacontenttype);
-            console.log(ce.data);
-            res.send(ce.type);
-            return;
-        }
-        res.send("not a cloud event");
+import { getCloudEvent } from 'sdk';
+
+export function main(req, res) {
+    const ce = getCloudEvent(req);
+    if (ce) {
+        console.log(ce.type);
+        console.log(ce.source);
+        console.log(ce.specversion);
+        console.log(ce.id);
+        console.log(ce.time);
+        console.log(ce.datacontenttype);
+        console.log(ce.data);
+        res.send(ce.type);
+        return;
     }
+    res.send("not a cloud event");
 }
 ```
 
@@ -243,17 +239,15 @@ module.exports = {
 
 ```javascript
 // After
-const { emitCloudEvent } = require('sdk');
+import { emitCloudEvent } from 'sdk';
 
-module.exports = {
-    main: async function (req, res) {
-        await emitCloudEvent(
-            'com.example.order.created',
-            '/orders',
-            { orderId: '123' }
-        );
-        res.send("event emitted");
-    }
+export async function main(req, res) {
+    await emitCloudEvent(
+        'com.example.order.created',
+        '/orders',
+        { orderId: '123' }
+    );
+    res.send("event emitted");
 }
 ```
 
@@ -337,6 +331,7 @@ The following environment variables were renamed in the new runtimes. The `FUNC_
 | ------------------------------ | ------------------------ | ------------------- | ------------------------------------ |
 | `FUNC_HANDLER`                 | `HANDLER_FUNC_NAME`      | nodejs26, python314 |                                      |
 | `MOD_NAME`                     | `HANDLER_MOD_NAME`       | nodejs26, python314 |                                      |
+| `KUBELESS_INSTALL_VOLUME`      | `HANDLER_PATH`           | nodejs26, python314 |                                      |
 | `REQ_MB_LIMIT`                 | `FUNC_BODY_MB_LIMIT`     | nodejs26            |                                      |
 | `FUNC_MEMFILE_MAX`             | `FUNC_BODY_MB_LIMIT`     | python314           | Unit changed from bytes to megabytes |
 | `KYMA_INTERNAL_LOGGER_ENABLED` | `SERVER_INTERNAL_LOGGER` | nodejs26, python314 |                                      |

docs/user/00-90-runtime-deprecation-schedule.md

@@ -9,7 +9,6 @@ This document outlines the planned deprecation and end-of-life (EOL) dates for s
 | Node.js 20 | February 2026 | April 2026 |
 | Node.js 22 | July 2026 | November 2026 |
 | Node.js 24 | TBD | TBD |
-| Node.js 26 | TBD | TBD |
 | Python 3.12 | September 2026 | March 2027 |
 | Python 3.14 | TBD | TBD |
 

docs/user/technical-reference/05-20-env-variables.md

@@ -14,6 +14,7 @@ Every runtime provides its own unique environment configuration which can be rea
 | **HANDLER_FUNC_NAME**        | `main`                                                                        | The name of the exported Function inside the `HANDLER_MOD_NAME` file.                                                                                                         |
 | **MOD_NAME**                 | `handler`                                                                     | Deprecated. Use `HANDLER_MOD_NAME` instead. Supported only in nodejs20, nodejs22, nodejs24, and python312.                                                                     |
 | **HANDLER_MOD_NAME**         | `handler`                                                                     | The name of the main exported file. It must have an extension of `.py` for the Python runtimes and `.js` for the Node.js ones. The extension must be added on the server side. |
+| **KUBELESS_INSTALL_VOLUME**  | `/kubeless`                                                                   | Deprecated. Use `HANDLER_PATH` instead. Supported only in nodejs20, nodejs22, nodejs24, and python312.                                                                         |
 | **HANDLER_PATH**             | `/`                                                                           | Full path to volume mount with user's source code.                                                                                                                             |
 | **FUNC_RUNTIME**             | None                                                                          | The name of the actual runtime. Possible values: `nodejs20` - deprecated, `nodejs22`, `nodejs24`, `nodejs26`, `python312`, and `python314`.                                    |
 | **TRACE_COLLECTOR_ENDPOINT** | None                                                                          | Full address of OpenTelemetry Trace Collector is exported if the trace collector's endpoint is present.                                                                        |                                                      |

docs/user/technical-reference/07-70-function-specification.md

@@ -371,7 +371,7 @@ You can use a custom runtime image to override the existing one. Your image must
 
 - Expose the workload endpoint on the right port
 - Provide liveness and readiness check endpoints at `/healthz`
-- Fetch sources from the path under the `HANDLER_PATH` environment
+- Fetch sources from the path under the `KUBELESS_INSTALL_VOLUME` environment
 - Security support. Kyma runtimes are secure by default. You only need to protect your images.
 
 Every Function's Pods container has the same system environments, which helps you configure the Functions server. For more information, read the [Environment variables](05-20-env-variables.md) page.

docs/user/technical-reference/07-90-runtime-deprecation-schedule.md

@@ -0,0 +1,35 @@
+# Function Runtime Deprecation Schedule
+
+This document outlines the planned deprecation and end-of-life (EOL) dates for supported Function runtimes in Kyma Serverless.
+
+## Supported Runtimes and Deprecation Timeline
+
+| Runtime | Planned Deprecation | Estimated EOL |
+| --- | --- | --- |
+| Node.js 20 | February 2026 | April 2026 |
+| Node.js 22 | July 2026 | November 2026 |
+| Node.js 24 | TBD | TBD |
+| Python 3.12 | September 2026 | March 2027 |
+| Python 3.14 | TBD | TBD |
+
+## Deprecation History
+
+### Node.js 20
+- **Status**: Deprecated
+- **Deprecation Version**: v1.10.0
+- **Details**: Node.js 20 runtime was deprecated starting with version 1.10.0. For more information, see [this issue](https://github.com/kyma-project/serverless/issues/2231).
+
+> [!NOTE] 
+> The deprecation and EOL dates listed in this document are **predictions based on current release cadence and Node.js/Python LTS schedules**. These dates are subject to change and may be adjusted based on the following:
+> - Changes in the Kyma Serverless release schedule
+> - Updates to upstream Node.js and Python LTS timelines
+> - Community feedback and requirements
+> - Security considerations
+>
+> Always check the [release notes](https://github.com/kyma-project/serverless/releases) for announcements regarding runtime deprecations and EOL timelines.
+
+## Recommendations
+
+- Plan upgrades to newer runtimes well in advance of deprecation dates
+- Monitor release notes for any changes to this schedule
+- For Functions using deprecated runtimes, migrate before the EOL date to avoid service disruption