[nicburgt]

I'm still tweaking the demo in the coming days, but it is E2E working. I'm still not a fan of the clarity of the comparison chart, but i'll keep churning on that.

For now, the flexmeasures setup in the example/demo looks as follows:

With a combination of flexible/inflexible loads,

The demo scenario is configured to initially only generate a plan (with only pricing input) and afterwards generate a plan with both pricing and OpenADR input.

The comparison chart/html currently looks as follows (this part is still WIP):

comparison.html

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	openadr3-client@​2.1.0 ⏵ 2.4.0			+1
	ruff@​0.16.5 ⏵ 0.16.6	+1
	types-requests@​2.33.0.20260712 ⏵ 2.33.0.20260906

View full report

[Flix6x]

It looks like these .github instructions are copied from the flexmeasures repo. I think it would make sense to view these as being applicable to the FM server and all FM plugins (basically FlexMeasures organization-wide). I see 3 ways forward:

1. Keep the files in flexmeasures only, and have plugins (including the flexmeasures-plugin-template repo) point to them in their AGENTS.md. Not sure if agents will respect that.
2. Move the files to the tsc (or a new dedicated) repo under the FlexMeasures organization. Same uncertainty as 1.
3. Have them duplicated in each plugin, and keep them in sync (perhaps through a dedicated test in the plugin, against the instructions set in the flexmeasures repo).
4. Have them duplicated in each plugin; accept diverging.

Do you want to try 1, which would be my preference? I'm afraid you happen to be the first plugin author to face this issue.

[Flix6x]

runs at confused me. Is the seed based on the day at which:

1. the user runs the script,
2. the belief_time of the forecasts reside in, or
3. the events that are being forecast reside in?

If it is 2, then I suggest:

Suggested change

	always gets the same numbers, whether the script runs at dawn or at noon, and a re-run
	always gets the same numbers, whether the forecaster runs at dawn or at noon, and a re-run

[Flix6x]

I suggest refactoring to share a single definition of the environment settings across 4 services.

[nhoening]

For the record, I ran this myself (mostly successful), and send Nick my comments per email a few days ago. Also, Nick showed this demo successfully at the LF Energy Summit this week.