WIP: refactor ref int#230
Conversation
There was a problem hiding this comment.
Can we move the skills to eclipse-score/.github#56. It contains a copier template to centralize AI stuff
There was a problem hiding this comment.
same here, please add it to eclipse-score/.github#56
There was a problem hiding this comment.
00df701 to
426b188
Compare
| import os as _os | ||
| import sys as _sys |
There was a problem hiding this comment.
why like this? why not import directly without renaming namespace?
| def _patch_needpie_suppress_legend() -> None: | ||
| """Suppress all in-chart legends in sphinx-needs needpie charts.""" | ||
| try: | ||
| import matplotlib.axes |
There was a problem hiding this comment.
where matplotlib should be added as dep? In //:ide_support dependencies?
Or in final repo where it is used e.g. here ref_int?
There was a problem hiding this comment.
Im affraid that this kind of static dashboards will be outdated very quickly and hard to sync. I dont see any script that auto generates it here
| .. toctree:: | ||
| :titlesonly: | ||
|
|
||
| S-Core v0.7 <score_07> |
There was a problem hiding this comment.
can we put a wildcard here * so we dont need to maintain the list?
|
The created documentation from the pull request is available at: docu-html |
7a14192 to
70aa15d
Compare
6692efd to
02f64fc
Compare
The path docs/s_core_v_1/verification did not exist and was not created, causing the unit-test/coverage script to crash with FileNotFoundError. Use the existing docs/verification_report directory (and create it if missing) for both the script output and the workflow summary step.
Sphinx (warnings-as-errors) failed because docs/s_core_v_1/index.rst and docs/verification_report/platform_verification_report.rst were referenced via grid-cards but not listed in any toctree.
- Repin score from 5b8a1e34 to 1b51518e (81 source-link URLs) - Baselibs PA3 Component Architecture: 164/166 -> 165/167 skill(overall-status): clean up and fix checklist counter - Restructure SKILL.md (1063 -> 517 lines): drop migration notes, duplicated callouts, and the empty 'Complete RST Snapshot' section. - Specify counting model in plain prose (no formulas). - Fix count_checklist_status: chklst_*.rst stores :status: indented inside the .. document:: block, not at column 0. Updated section 3.3 and the Step-2 helper accordingly.
…eneration in SKILL
- Add docs/_assets/pa{2,3,4,5}_*.svg charts showing release evolution
(v0.5.0-beta -> v0.6.0 -> v0.7.0 -> current main) above each PA
module-tracker table in overall_status.rst.
- Embed via .. figure:: directives with alt text and width.
- Extend .github/skills/overall-status/SKILL.md (sec. 6a) with:
- release pinning recipe (annotated-tag deref, known_good schema diffs,
'now' = known_good.json on main of reference_integration)
- per-chart metric table and SVG generation workflow
- Communication vs. Some/IP double-count guard (applies to all PAs)
- rule that charts use TOTAL directive count, not valid-only
- PA5 split: historical bars from TEST-macro regex, 'now' bar from
PA5 RST table column sums; documented divergences.
…ion, fix label warnings - PA1: render FR issue titles next to the issue number; restrict #549 to Baselibs; add #757 'qualified json-parser' to Baselibs (no milestone); drop #914/#917 from Communication (local IPC scope only) - PA5: drop per-module Platform Ver. Rpt column; add prominent Platform Verification Report admonition after the table - PA5: split test counts onto a separate line-block line below the status emoji - PA5: add reader notes for C0/C1 coverage source and Static/Dynamic analysis semantics - Add cross-reference labels (overall_status_pa2..pa5) to fix six Sphinx 'undefined label' warnings from pi1/pi2/pi3 - custom.css: neutralise blockquote/line-block styling inside list tables so secondary lines blend into the cell; style new .platform-ver-report admonition Sphinx build now reports 0 warnings, 0 errors. SKILL.md updated to document all of the above (sections 4.0, 4.2, 5.0, 5.1, 5.2).
db13820 to
c3da6e5
Compare
This PR is a proposal and WIP. It can contain errors or other mismatches. In case this PR will be technically agreed, there will be an official request for review.