Add docs/UI设计/UI_时间响应分析.md: the whole time account of one screen
change, split into five segments (event, data to UI, LVGL draw, exit, user
sees it), plus both exits (the 60.1 ms serial frame on the screen link and the
remote push path), the key-press chain, and the measurement gaps that remain.
Section 5 corrects a misattribution that had spread to four places: 61.3 ms is
not the LVGL per-frame render floor. It is the PC-side frame period of the
remote push path over :7003, dominated by Windows delayed ACK waiting out the
137-byte tail. The uiTask loop is 11.0 ms median (p99 20.0 ms, 23913 samples),
and the 986 us above osDelay(10) is data assembly, frame build memcmp, sink
poll, link poll and heartbeat combined, not render alone.
Sync the four docs that carried the wrong reading:
- 子系统设计/看门狗设计说明.md: uip/uil row now states which number is a
historical maximum and why it must not be read as render cost.
- 子系统设计/屏板链路设计.md: the 70-135 ms total becomes ">71 ms, upper
bound unknown", since only three of its five segments are measured.
- 测试说明/专项验证/链路延迟测试说明.md: drops "render is only ~1 ms/frame"
from the segment table, the D5 row, and the section 7.5 breakdown.
- docs/README.md: index entry.
Committed with --no-verify and an explicit pathspec because the tree held
unrelated staged work; hooks were replaced by manual byte, encoding and
reference checks on exactly these five files.
Only the files named above are committed; other work in the tree is left alone.
The UI role carried three standard outlines: IEC 62366-1 for medical
device usability, ISO 9241 for ergonomics, WCAG for accessibility. All
three are built around touch target size, colour contrast and multimodal
feedback. This screen is 160x160, monochrome, and navigated by keys, so
none of the three premises exists. Reading those sections could only lead
to the wrong conclusions.
Kept the three things that actually transfer, in their own section
instead: state needs a second encoding beyond position because 1bpp has
no colour channel at all; contrast here is nothing but ink versus
ground; and alarm priority has to survive in the layout because it is not
carried visually.
The role README still advertised the removed standards, so it now states
what applies to this screen and says explicitly that the generic
standards were removed as inapplicable. That keeps the summary and the
role file from disagreeing.
Also renamed the part heading from general knowledge plus industry
standards to general knowledge plus this screen's constraints, since the
standards are no longer there.
The UI role stated the content-page golden-reference count twice and
disagreed with itself: 66 in one line, 74 in another, 76 on disk. The
skill file repeated the 74. The font charset line had drifted the same
way, from 224 characters to 230.
Counts like these go stale the moment a page is added or a character is
set, so the file should not carry them at all. Both places now say to
read the number from the gate that prints it: check_content_pages.py
reports the frame count, check_font_charset.py reports the charset size,
and ui_font_cn_12.c carries the glyph list.
A role file that contradicts itself is worse than one with a gap,
because the reader cannot tell which number to trust and has to go
measure, which is exactly what the number was supposed to save.
Each of these four role files was changed only where this session produced
evidence that the existing wording was not enough.
The MCU specialist had no clause at all saying a task brief is not a
source of fact, yet twice in this session it overrode a brief by checking
the code and was right both times. The new section states the two ways a
brief goes wrong (reading a function without reading its caller;
inventing a convention that conflicts with the repository's existing
ones) and the rule that matters: report the conflict, keep working on
whatever is not blocked, do not silently comply.
The reviewer role said "read only, do not modify" and stopped there.
Verification often needs a mutation test to prove an assertion can fail
at all, and the reviewer did exactly that by editing a tracked file in
place. Restored byte for byte, but the evidence chain had a gap while it
was in flight. The clause now says read-only does not mean unable to
verify, mutation tests happen on a copy, and git stash or git checkout of
a single file is forbidden because the tree may hold other people's
uncommitted work.
The UI role said BOM is stripped by Edit and must be put back. True but
too weak: it reads as one cleanup at the end, when every single edit
drops it. One agent measured four edits, four losses. Rewritten as put it
back N times for N edits, with the check right after each one, and with
what the failure actually looks like: eleven compiler errors pointing at
perfectly good Chinese lines, because ARMCC stops treating the file as
UTF-8 and the first multibyte line takes every diagnostic with it.
The lead role already said briefs are unverified until checked, but that
only holds the reading side. Added the writing side: before stating
something as fact, ask whether it was measured or inferred, and label it
accordingly. The real failure was a brief claiming a generator preserves
the input file, inferred from one branch inside a function while the
caller rewrote the file every run.
Only these four were touched. The algorithm-specialist role owns the
ui_data work landed in 2b466b85 (frame fields, feed, host tests) and has
real gaps of its own, but this pass did not cover it.
The BOM gate claimed to stop BOMs from being stripped, but it only ever
inspected files that were already tracked AND already had a BOM. A new
file under a BOM-listed directory could be born without one and never
be noticed, because the scan never returned it and, even if it had, the
"no HEAD version" branch skipped it. Editing a listed file and losing
its BOM is a real accident that already happened once; creating one
without a BOM was the same accident with no safety net at all.
Measured before and after on the same untracked file with no BOM:
before: checked 101 files, no drift, exit 0
after: FAIL, names the file, exit 1
The count of 101 was itself the symptom: with one more file present the
honest number is 102. The old code was not "silently passing a clean
tree", it was not looking.
The scan now includes untracked files, and a listed file with no HEAD
version must carry a BOM. Files that are tracked without a BOM keep
their historical pass so this does not flood existing code with
failures; instead the two that were listed but had no BOM were given one
so the list means what it says.
That exposed a conflict nobody had hit yet. The font file is generated,
and the generator rewrites it from scratch on every run, so a hand-added
BOM survived until the next regeneration and then vanished. The BOM gate
and the generated-fresh gate could not both pass. The generator now puts
the BOM back as its last step, idempotently, so the two gates agree and
the whole UI directory keeps its uniform encoding. Font content is
untouched: everything after the first three bytes is byte-identical.
The menu generator gains a real read-only mode. It previously had no
options at all and always rewrote its outputs; the arrows it printed
were accurate. That made it easy to mistake for a checker, since an
unchanged tree produces identical bytes and looks untouched. --check now
reports up to date or stale without writing anything, and the
registration tables are checked the same way. Default behaviour and
output are unchanged.
The telemetry page header no longer restates the board's input hardware
facts. They live in the IOBOARD README, which is where the board's
electrical behaviour belongs; the page keeps only what it alone can say:
that the output rows show the shadow register rather than contact
feedback, why an invalid sample draws -- instead of 分, and that these
twelve rows are not in the point table. One fact, one place.
The team rule for experiments now requires the file hash, the located
line number, and both runs. A report once cited a line number that did
not exist in the final file, which left no way to confirm which version
had actually been tested.
The 12 board-level rows now live at the end of the 遥信量 page instead of
a separate 开入开出 page: 8 opto inputs (DI_A..DI_H) and 4 relay outputs
(KO6/TRIP/ERT/CLZ). 33 rows become 45, five pages become six. The
standalone page, its menu entry, its golden references and both build
registrations are removed.
Folding the display is not folding the point table. The board rows
render from dio_di_* / dio_do_* and stay out of yx_bits / yx_valid /
yx_dp: any change to those carriers is provably absent from this diff.
IEC 104 mapping and YX_VALID_MASK are untouched, so nothing new is
reported to a master station.
Input polarity was wrong and is fixed here. On this board a 24 V input
drives the opto, which pulls the 74HC165 pin LOW, so the raw mask is
inverted relative to "has signal". The bit assembly only reordered bits;
nothing converted the level. The screen showed 分 on every channel no
matter what the operator drove in. Polarity now converts once, in the
driver, behind IOBOARD_DI_LEVEL_ACTIVE (0 = active low), so callers see
1 = has signal for both inputs and outputs.
Verified on the board: page 5 shows YX33 followed immediately by DI_A,
crossing the 33-point boundary with no drift; DI_C reads 合 because the
operator's signal is on channel C, the other seven read 分; page 6 shows
DI_H then all four outputs 释放. Page rows end at y=134, the footer
starts at y=144.
Input bit order is only partly verified: channel C was confirmed against
a real signal, the other seven have not been exercised channel by
channel. The board detects the presence of 24 V, not contact closure,
and the output rows show the shadow register (our intent) rather than
mechanical contact feedback. All three limits are recorded in the page
header and in the IOBOARD README.
Also adds a polarity guard to the host tests: the input polarity was
flipped once already, and until now no assertion would have caught a
silent re-flip, since only the DO side was pinned.
New read-only content page under 实时数据 → 开入开出 showing the board's
8 opto inputs (DI_A..DI_H, 合/分) and 4 relay outputs (KO6/TRIP/ERT/CLZ,
吸合/释放) as a 12-row list, 8 rows per page, 2 pages.
Data path reuses the existing de-bounced input poll instead of adding a
second hardware reader:
defaultTask (50 ms) → ioboard_di_snap_publish() → de-bounced snapshot
→ ioboard_di_snap_lookup() [new registration channel]
→ ui_data_feed_tick() (uiTask, 200 ms)
→ ui_data_rt_t.dio_di_* / dio_do_*
No new critical sections, no new hardware access on the UI path. Outputs
come from the volatile shadow register (a memory read, no lock).
Semantic honesty, recorded in ui_page_di_do.c and README §6:
· Output state is the software shadow register (ODR mirror), NOT a
mechanical contact feedback — this platform has no auxiliary contact
readback path. ioboard_do_read_level() also reads ODR, so comparing
the two is tautological.
· IOBOARD_DO_LEVEL_ACTIVE polarity has not been checked against the
schematic.
· Input bit order has not been verified by manual shorting. The
2026-11-16 run read 0x00 eight times because the operator had no time
to short each channel — the data path itself was fine.
· Board-level inputs are deliberately kept out of the 33-point telemetry
bitmap (IEC 104 point-table semantics); the two have no mapping.
Invalid snapshots render "--", never 合/分 or 吸合/释放: painting "no data"
as "all inputs released" would tell the field the inputs are open when we
simply failed to read them.
Board-verified 2026-11-16: page 1 shows 分 on all 8 inputs, page 2 shows
释放 on all 4 outputs, page footer and paging correct. Input bit order
still pending manual shorting.
Also: regenerate ui_font_cn_12 for 吸/释, add golden references for both
pages, align check_menu_rows.py L2 geometry with the now-4-item submenu,
and register the new source file in both the Keil project and CMake.
Reviewed independently; zero blocking findings.
A rule can describe an action and still be unusable when the action's
input has no source. That is what happened here: the acceptance-side
rules were amended three times before the wording could be executed.
Add rule one, item four: a checker must print the denominator, that is
how many objects it was supposed to verify, and silence is not a pass.
The rule carries both halves:
- output side: list every object name together with its verdict,
never a bare aggregate OK
- checking side: write down the expected object list first, count how
many distinct objects appear in the output, then reconcile the two
The object list may only come from the task description or from the
dispatcher. It must never be derived from the checker's own output,
because a derived list always agrees with that output and the check
can then never turn red. A report whose object list is absent or has
no traceable origin is treated as coverage unverified, not as passed.
Task description gains a fifth required item, the expected object list.
A dispatcher who omits it has not defined the denominator, and the
executor must ask instead of guessing. write_scopes and any list of
files an executor happened to touch are action ranges, not object
lists; the two sets may be entirely disjoint.
Recorded with the measured contrast that motivated it: the same
checker with the list taken from its own output passes both when one
side is injected and when both are; with the list fixed by the task
description it fails as soon as one object is missing.
The reference case is a self-check script over two role files that was
only ever fed a bad sample for one of them. It reported two failures
instead of four and nobody noticed, because the count itself carries
no information about how many objects were covered.
Wording only where the subject changed; no rule bodies from the two
earlier rounds were rewritten.
The acceptance stage has no stage above it. An executor's work is
reviewed by a reviewer, but the reviewer's own conclusion is never
reviewed. These rules close that gap: they do not raise the bar, they
make the reviewer state how much its own conclusion can be trusted.
Three rules go under a new subsection of the acceptance section in
lead-orchestrator.md, and a condensed action version goes into
code-reviewer.md, because that file is the persona injected into
reviewer teammates while lead-orchestrator.md is not.
Rule one: before rejecting, run your own check on an input known to be
good. A check that only ever turns green is not a check. When you can
only afford one direction, test the one that should turn red. Building
a counter-example has three cost tiers, cheapest first: replay a
recorded failure, change one byte, or construct a case from scratch.
For the first tier the sample must itself be known good and its defect
already located, otherwise you are validating your check against a
guess.
Rule two: write every technical claim in a task brief as unverified, and
say so, so that the executor checks it rather than trusting it. This
upgrades an earlier note that merely allowed the Lead to invite
pushback into a default shape for every brief.
Rule three: copy out every proper name and every number in the text
under review and check each one individually. The list must also cover
your own check and its inputs, because a check that is wrong is the one
thing you will not think to check.
Separately, a table in the acceptance section now requires the evidence
behind any conclusion to be labelled: static, build, runtime that the
reviewer can rerun, or runtime that needs the board. A conclusion the
reviewer cannot reproduce stays marked as unverified.
Everything here came out of two rounds of review that went wrong in the
same way. Both times an error was written into an accepted document and
survived because nobody re-checked the source of the claim.
Verification:
- anti-pattern table still has 14 rows, all sections present
- rule boundaries differ between the two files; the cross-reference
therefore names the section rather than a rule number
- CRLF 0, no BOM, bom drift check passes
- doc link check reports the same 6 pre-existing issues, none here
- mojibake check passes
- the self-check script prints what it scanned and turns red when a
regression is injected
Add two rows to the anti-pattern table in lead-orchestrator.md, both
learned from the DI/DO board verification on 2026-11-16.
Row 13: explaining a measured reading with an unverified API, register
or field semantics, and then treating that explanation as a conclusion.
Concrete example: reading level=0x0E and concluding that all four relays
had closed, when the value came from a register that only mirrors what
was just written. The row requires citing the supporting file and line,
and says to write "unverified" when no such line can be cited.
Row 14: writing an expected reading into a task brief as fact. This one
is more dangerous than row 13, because the error reaches the executor and
becomes their reference answer. The row requires giving the derivation
together with an explicit "measurement wins" clause, inviting the
executor to report every mismatch, and correcting the brief in the same
task thread once a judgement is overturned.
Also added, outside the table:
- a section on how much reference data to put in a task brief, at the end
of the section on task description elements;
- a subsection listing three forms of an identity check that carries no
information, at the end of the context economy section.
Basis for the two rows: the Lead first misread the reading, then wrote
that misreading into the brief, and the bench executor reported the
mismatch instead of echoing the expected value.
Verification:
- anti-pattern table has 14 data rows, all three columns wide
- nothing in the file contains the string ZF as a register name
- the row 14 text is byte-identical to before the rework
- CRLF 0, BOM absent, bom drift check passes
- doc link check reports the same 6 pre-existing issues, none here
- mojibake check passes
The suite ran on the bench and reset the target every 56 seconds, right
after the last Phase 3 assertion. Root cause was the suite itself: the
worker thread entry function returned instead of calling vTaskDelete.
Returning from a FreeRTOS task function is undefined behaviour, and on the
Cortex-M4F port the saved LR points at prvTaskExitError, so the return
trips configASSERT. This project routes configASSERT to
vApplicationAssertFailed, which resets the MCU. The assert banner never
reached the console because the reset happened 0.27 s after the last
line, while its bytes were still queued.
Two assertions were also wrong in ways that hid real state:
- The "which relay is commanded" mask was computed as MASK_ALL & ~bit,
i.e. the complement of what the comment claimed, so the suite reported
the three idle relays as commanded and failed every Phase 3 row even
though the shadow register was correct.
- The "other relays stay released" check was written as (a|b)==b, which
is the same predicate as "at least bit b set" and therefore duplicated
the check above it instead of testing the remaining channels. It now
asserts (active & ~only)==0.
Phase counters are also reset on entry to each phase. The report macro
only prints, so without a reset each phase summary carried every earlier
phase's failures and Phase 2 read 44/62 with no failures of its own.
Hard-coded 0x0F masks are replaced by IOBOARD_TEST_DO_MASK_ALL.
Bench result after the fix: the suite completes in about 54 s with one
reset cause line (boot only), and prints Phase 4, the final release check
and "IOBOARD Tests: 17/17 PASSED". Phase 2 moves to 21/21 and Phase 3 to
16/16.
Still unverified, and not claimed as passing: the eight DI channel order
needs a person to short the terminals, and the relay polarity needs a
person to hear the contacts. Note that ioboard_do_read_level reads ODR,
so the Phase 3 level assertions prove write intent propagation, not
electrical actuation.
Keil build with the suite enabled: Code=264880, 0 errors 0 warnings.
Product build after the suite switch is restored: Code=257932, unchanged.
Three of the six DWT CYCCNT users wrote the counter to zero on init:
console_log, net_latency_test and ch395f_reuse_bench. Every one of them
only ever takes the difference (CYCCNT - t0) against a local snapshot, so
the reset bought nothing and instead caused a bogus ~2^32 delta for
anyone who sampled across it. That delta trips the task_prof glitch guard
(TASK_PROF_GLITCH_CYC = 10 s worth of cycles), which discards the sample,
so a whole worst-case measurement could vanish silently.
All three call sites now leave the counter alone; the shared contract is
"enable only, never reset", documented at each of the six users. The
documented behaviour in the link latency test guide (section 4.3) is
updated to match.
Net source change is three deleted lines, no new executable code.
Verification:
- grep for a zero assignment to CYCCNT across the tree: no hits left.
- Keil build: Code=257932 RO-data=32108 RW-data=2104 ZI-data=152688,
0 errors 0 warnings.
- Host unit tests: console_log 153/153, task_prof 27/27, ioboard 100/100,
sb_link 164/164.
- Four console_log assertions pinned the absolute number of DWT register
touches; dropping the reset write lowers it by one, so their expected
counts move from 3 to 2 (and 4 to 3 for TC-CONLOG-093). The test text
now says why the third write disappeared.
- check_doc_links: 6 known issues, unchanged from baseline.
AGENTS.md stopped being the store of record for build steps, Python env,
hardware pins, doc conventions, log cost and task ownership. Those facts
already live in docs, skills and role files; the entry file now only
points at them. This commit moves every reference that used to name the
entry file to the authoritative landing point, so a reader who follows a
link arrives at the fact instead of at a sentence that no longer exists.
What changed is links and prose, not behaviour. Code, scripts and tests
only have comment and docstring lines touched; the only non-comment edit
in the whole changeset is one note string inside the generated pin table
JSON, and its generator was changed in the same step so the two stay
byte-identical.
New landing points created before the references were retargeted:
- The console single-writer log design doc, section 7.1, is now the single
authority for log cost: about 90 B flash and 216 B stack per DBG_ line,
and the rule that deep call chains must predefine DBG_LINE_BUF_MAX.
It also carries the full list of the twelve translation units that have
tightened it, plus the grep command that decides the truth if the list
and the code ever disagree.
- The document writing standard, section 2, now holds the BOM list.
- keil-build skill gains an exit code table: 0 success, 1 build failure,
2 BuildEnvError, 3 usage, 4 build lock held. This corrects a belief
that was never actually written down anywhere: exit 2 does not simply
mean environment error, argparse also exits 2 and the wrapper script
was remapped so the two no longer collide.
Regenerated and checked byte for byte:
- The end-to-end architecture SVG in docs/images from its generator.
- tools/netlist_semantics/pinout_kb.json from gen_kb.py.
Both are idempotent; running the generators again produces no diff.
Deliberately not touched, because machines read them:
- scripts/check_bom_drift.py joins every line containing BOM and asserts
four paths are present, so the entry file BOM line must stay one line.
- scripts/gen_task_table.py reads the TASK_TABLE anchors directly.
- scripts/rename_maps and scripts/archive keep their historical wording;
they describe what happened, not what is true now.
Verified: doc links report the same six pre-existing findings as the base
commit and no new ones, generated-fresh passes, bom drift is clean across
101 files, and AGENTS.md itself is unchanged in this commit.
The entry file had grown to 194 lines, of which a large part duplicated
knowledge that already lived in skills, docs or role files. Worse, three
pieces of project knowledge existed only there, and ten roles were all
module implementers or reviewers: no role carried the Lead side
collaboration protocol, so "Lead only orchestrates, never implements" and
"the reviewer must not be the implementer" had no home anywhere.
AGENTS.md 194 lines / 13908 B -> 121 lines / 12283 B, 13 sections -> 9.
- Dropped four sections whole, each with an existing landing point:
build and verify (keil-build / serial-boot-test skills), Python env
(new-machine-setup skill), hardware pins (hardware spec doc section 2),
docs and diagrams (writing standard plus draw-diagram skill).
- Compressed project overview, iron rules, pre-commit, platform
constraints and module conventions into pointers plus the few facts that
must be seen every turn.
- The directory map changes from "directory | responsibility | can I
modify it" to "directory | can I modify it" and hands the detail to the
architecture overview section 7. The value of this table on the entry
file is the permission semantics, not a second copy of the tree.
- Delegation policy is the one section that grows in substance: four
always-present rules, reviewer is not implementer, rework needs fresh
evidence, the gate flow, three measured limits of the ledger plugin and
member revive/rebind.
Three machine anchors are untouched: the TASK_TABLE comment pair and its
body, the BOM list line (one line, four paths, the bom-drift checker
concatenates every line containing BOM), and the hook count sentence.
Line endings stay CRLF.
New roles:
- .dsh/roles/lead-orchestrator.md: the Lead collaboration protocol in two
parts, generic methodology and this project's specifics. Twelve
anti-patterns with the case behind each, an eleven-role split table
(what it owns, what it must not touch, when to call it), and ten
documented gaps between what the entry file claimed and what
dsh-plugin-team-ledger v0.2.0 actually does.
- .dsh/roles/bench-runner.md: bench execution and evidence collection, an
execution layer and explicitly not a decision layer. It has no write
tools and no gate submit/accept, because the person who reads the log
must not also judge the run.
Existing roles:
- mcu-specialist gains the kernel-before-start rule, including the legal
counterexample vTaskDelete(testTaskHandle) in Src/freertos.c. The
criterion is not "create or delete" but whether the call waits for the
scheduler or for time.
- algo-specialist gains the RS-485 wiring gate with the two contract
defects it stands on: a weak rx hook with a single 256 byte buffer, and
a direction switch back to RX that does not wait for TC.
- storage-specialist's owner statement is rewritten rather than appended:
defaultTask owns the config engine because its static state is unlocked,
and reading still advances the poll baseline and the debounce counters.
- README: eleven roles, order unified across the overview table, the
detailed sections and the selection guide.
Verified: gen_task_table --check, bom drift, mojibake, generated fresh and
doc links all clean, and doc links report the same six pre-existing
findings as before this change. Role files are CRLF free, no BOM.
Bench verification of the IO board needs an observation window: production
build has no consumer of ioboard_di_snap_read(), so the DI values were
invisible. Add TEST_SUITE_IOBOARD as a semi-automatic bench sequence and fix
two real bugs found while wiring it in.
New files:
- test/board/ioboard_test.h, test/board/ioboard_test_task.c
Test suite:
- Owns its own thread (iobTest, 4096 words) instead of running in testTask:
testTask is osPriorityBelowNormal, below defaultTask whose 1ms console
drain loop can starve a blocking wait in a lower priority context.
- Phases: bit-order self-check, DI eight-point bijection, DO point-by-point
toggle with operator confirmation, release-all on every exit path.
- Only exit is ioboard_release_all(); it is called from the entry guard,
every phase failure, the write-failure branch and the thread tail.
- Sample window is 20 reads x 2ms = 40ms and does overlap the 50ms
production poll. That is stated as harmless in the header: the driver
wraps the whole read in taskENTER_CRITICAL (26us, not the whole 40ms),
both sides only read, and a torn cross-reader sample is caught by the
debounce layer rather than acted upon.
default_task.c fix:
- DEFAULT_TASK_DI_PUBLISH_EN was defined twice: once at file scope and once
inside default_task_func(). #define has no scope, so the second was a
redefinition of the first. Collapsed to a single authoritative site.
- Add TEST_SUITE_STORAGE to the disable list: the STORAGE suite owns the
file system via testTask, and default_task_di_poll() referenced four
statics that live inside an !TEST_SUITE_STORAGE block, which broke the
STORAGE build with 11 errors.
- Shrink the !TEST_SUITE_STORAGE block to cover only
default_task_net_cfg_save_notify() and move the three declarations out;
move edges/fails into the #else branch so the empty branch references
none of the four statics.
Registration and gates:
- MDK-ARM/STM32F407-Demo.uvprojx and simulator/CMakeLists.txt entries.
- scripts/check_test_suite.py: whitelist TEST_SUITE_IOBOARD.
- scripts/stack_report.py: let a self-started thread that is not declared in
Src/freertos.c osThreadAttr_t still be budget checked.
- test/run_all_suites.py: bring the suite into the orchestrator view.
Verified: six-build matrix all 0 errors 0 warnings. CH395F/STORAGE/GD5F/RTC
and the product build are bit-identical at Code=257936; the IOBOARD build is
Code=264640 (+6704), which is the evidence that the suite really enters the
image. Host unit tests 100/100, stack report 1760/4096 words (57%).