[thiagoralves]

• Rewrites the RTC block (libs/sources/additional-function-blocks/rtc.st). Its predecessor was carried over from MatIEC's LGPLv3 library, which Autonomy does not own. Breaking behaviour change, decided in review: RTC is now a set-and-run clock. On its first scan it reads CURRENT_DT() once and counts from it with TIME(), so it starts at the system date (1970 plus uptime on targets without one, such as AVR). The IN input is renamed SET: while SET is TRUE, CDT equals PDT; when SET is FALSE, CDT keeps counting from the last value set. Q copies SET. Projects that wire IN must rename it to SET. The block's hover documentation describes this.
• PID, INTEGRAL, DERIVATIVE, RAMP and HYSTERESIS are IEC 61131-3 example blocks: their headers now cite the standard instead of MatIEC. Those five carry no Autonomy header, since their code comes from the standard. All copyright lines read Copyright (c) <year> Autonomy® and every licence identifier reads GPL-3.0-only (with the runtime exception for the library).
• Adds the contribution setup shared with openplc-runtime: CLA.md, CONTRIBUTING.md, the PR template checkbox and a CLA check. Everyone ticks it, staff included; only bots pass without it. CLA.md is version 1.0. The README points to the runtime licensing page.

Ticket: RTOP-376 — https://autonomylogic.atlassian.net/browse/RTOP-376 (small change, no Requirements Gathering; no Cybersecurity Risk Assessment: library code, text and repository configuration only).

Testing

• New tests/library/additional-fb-rtc.test.ts (six ST cases through g++): never set (starts within 5 s of CURRENT_DT() and counts), SET TRUE, SET held, SET released, PDT ignored while SET is FALSE, setting again. Deliberately broken blocks (no set time; a 1970 start) fail the matching cases. npx vitest run tests/library: 489 passed; npm run typecheck clean.
• Packed and installed into openplc-editor: a project using RTC with located inputs and outputs compiled for OpenPLC Simulator, Arduino Uno, Arduino Mega, ESP32 Generic, ESP8266 NodeMCU, Raspberry Pico and Raspberry Pico 2. Every build calls CURRENT_DT() from the new RTC, AVR included.
• Manual test by the developer on hardware of the new behaviour: passed.

Contributor License Agreement

• I have read and agree to the Contributor License Agreement, version 1.0

🤖 Generated with Claude Code

https://claude.ai/code/session_01MRWeC5FUhe5ZwEEbLUGpZ6

[Gustavohsdp]

Review summary

The RTC rewrite is behaviourally equivalent to the previous block (edge detection, PDT latch, CDT = PDT + elapsed, Q := IN), the CLA workflow reads the PR body through env (no script injection), and the five IEC example blocks match the MatIEC originals apart from formatting and the header.

Validation run by the reviewer (Linux, node:22-bookworm + g++): npx vitest run → 104 files, 3474 passed / 7 skipped; npm run typecheck clean; npm run lint 0 errors. On macOS the g++-based tests fail at link time (tapi error: malformed file), which is a local toolchain problem and also hits suites this PR does not touch.

Findings (details inline):

Severity	Where	Problem
required	README.md:274	The OpenPLC Runtime licensing link returns 404: LICENSING.md only exists in openplc-runtime#225, which is still open and targets development, not main.
required	tests/library/additional-fb-rtc.test.ts:25	The IN = FALSE case only checks a delta, so the epoch base of CDT is not pinned. A mutant that uses DT#2000-01-01-00:00:00 + TIME() passes all six cases.
nit	libs/sources/additional-function-blocks/rtc.st:2	Only rtc.st gets an SPDX/copyright header; the other five .st files in the same library have none. The holder also reads "Autonomy", while CLA.md names "Autonomy Logic Inc.". Is that intentional?
nit	libs/sources/additional-function-blocks/rtc.st:9	The inline descriptions of IN, PDT, Q and CDT were dropped, and they were the only per-variable documentation for this block.
nit	.github/workflows/cla.yml:22	author_association can report CONTRIBUTOR for members whose org membership is private, so they would have to tick the box too. Harmless, but worth knowing.

Note (outside this PR): ci.yml only runs on pull_request to main, so PRs into development, this one included, get only the CLA check and no lint, typecheck or tests in CI.

[thiagoralves]

Review follow-up:

• Behaviour change (7edb04a): the RTC block is now a set-and-run clock and no longer matches the old block. It starts from CURRENT_DT() on its first scan (1970 plus uptime on targets without a system date), the IN input is renamed SET, CDT equals PDT while SET is TRUE, and it keeps counting from the last value set once SET is FALSE. Projects that wire IN must rename it to SET. The PR description and the hover documentation describe this.
• CI note (ci.yml only on PRs to main): outside this PR's scope, so not changed here. Library tests and the type check were run locally and are listed in the description.
• 04049ed: licence identifiers are GPL-3.0-only (with the runtime exception for the library), copyright lines read Autonomy®, CLA version 1.0.