Assert valid parameters

[cbrisebois-lasp]

Assert component default parameter values via Validate_Parameters

A component's Validate_Parameters function today runs only when a parameter operation arrives from the ground, so the default parameter values compiled in from the component model are never checked against any custom validation the developer implements there. An invalid default flies silently until the first parameter update. This PR closes that gap by asserting the defaults through Validate_Parameters both at assembly startup and in component unit tests.

What's generated

Components with parameters gain one new base-package primitive:

• Assert_Valid_Parameter_Defaults — asserts on a dispatching Validate_Parameters call against the component's working parameter copies, which hold the model defaults until the first parameter update. It lives in the base package because the working copies are traceable through the subprogram symbol and the assert's file and line.

Where it's called

• Startup: at the end of Set_Id_Bases — the one initialization step every parameterized component has (parameters always contribute Parameter_Id_Base), unlike Init_Base, which only exists for components needing heap setup.
• Unit tests: for a regular component, the generated tests base calls it in Set_Up right after allocating the tester — the tests base regenerates on every build, so existing tests inherit the check without touching their committed testers. For a generic component the tester is instantiated inside the developer's test implementation where the tests base cannot reach, so the call is emitted into the tester's Init_Base template instead and reaches existing generic tests as their testers are regenerated (the limiter is the only generic parameterized component in the repo, and is updated in this PR). Both hooks run before Set_Up_Test, while the working copies are still pristine defaults.

Design contract

Because the check runs before the component is connected or initialized, Validate_Parameters must be a pure function of its arguments — no dependence on Init state, no connector invocations. This was already the intended shape of the function; the calls make it load-bearing, and it is now documented at the override point in both the base spec and the implementation template.

Review notes

The four commits layer for review: (1) the primitive alone, (2) the startup integration, (3) the test integration, and (4) the patch to the limiter component. Generated doc comments in each commit describe only the behavior that exists at that point.

Verification

• Unit tests pass for every parameterized component in the repo: limiter (generic path, tester Init_Base hook), pid_controller (tests-base Set_Up hook), and the parameters component's test and test_grouped suites, whose testers call Set_Id_Bases directly and so exercise the startup assert at runtime.
• Negative proof: with a component's model default deliberately edited so its Validate_Parameters rejects it, the regenerated unit test fails during Set_Up with ADA.ASSERTIONS.ASSERTION_ERROR pointing at the generated assert; restoring the default returns the suite to green.
• A full downstream assembly build compiles cleanly with the regenerated autocoder output.

[dinkelk]

This is subtle. But can you look at what triggers this to have content in the component.py model. We need to mere existence of a parameters model to trigger this, even if a component doesn't have a Parameter_Update invoker connector. Weird case, but I want to make sure it is covered.

Currently the check is

365         if self.set_id_bases_parameters:

to which we might need to add or self.parameters or maybe CLAUDE has a more accurate solution here.

[cbrisebois-lasp]

Confirmed. Here's the path:

1. gen/models/component.py:134 — set_id_bases_parameters starts empty during component load.
2. gen/models/component.py:331 — every submodel attached to the component gets submodel.set_component(self) called.
3. gen/models/parameters.py:44-51 — the parameters submodel's set_component unconditionally appends parameter_Id_Base to component.set_id_bases_parameters as its first statement. No branch, no way to skip it.
4. gen/models/component.py:365-375 — runs after the submodel loop; since the list is non-empty, self.set_id_bases is set to a subprogram object (truthy). The None branch is unreachable for a parameterized component.

No need for or self.parameters there

[Jbsco]

This is also called at component-name-implementation-tester.adb:32, so would it run twice for every component with parameters? Might be able to drop the tester call, the one in name.adb also covers tests that never call Init_Base.

[Jbsco]

Maybe superfluous, but could add a message with the component type.