tirtc-device-builder 0.11.1 → 0.11.2

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "tirtc-device-builder",
-  "version": "0.11.1",
+  "version": "0.11.2",
   "description": "Codex workflows for building and validating TiRTC device firmware across supported chip platforms.",
   "author": {
     "name": "TangeAI",

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 This project follows Semantic Versioning.
 
+## 0.11.2
+
+- Make the LCKFB BK7258 XiaoTai development profile default to DEBUG logging,
+  with complete HTTP, MQTT and TiRTC/WHIP inputs and results available without
+  a separate diagnostic build; INFO remains available to suppress wire payloads.
+
 ## 0.11.1
 
 - Pin the BK7258 public baseline to the official Gitee

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tirtc-device-builder",
-  "version": "0.11.1",
+  "version": "0.11.2",
   "description": "Install and run TiRTC device-development Agent Skills across popular coding clients.",
   "license": "MIT",
   "author": {

package/skills/tirtc-beken-builder/SKILL.md

@@ -139,10 +139,9 @@ and its required active probes pass.
 Keep device keys, Wi-Fi passwords, MQTT/WHIP tokens, certificates, calibration
 data, MAC-derived identifiers, captured user audio and captured logs outside
 source control and generated reports. Use the conventional `ERROR`, `WARN`,
-`INFO`, `DEBUG` levels. Product/release firmware defaults to `INFO` and does not
-print complete network request or response payloads. A deliberately enabled
-`DEBUG` build may print complete HTTP, MQTT and TiRTC/WHIP inputs and results,
-including authorization values, for controlled integration work; handle that
-output as sensitive development data and return the build to `INFO` before
-release. Downloads, account access, flashing, erasing, factory-partition changes
-and publishing a reusable board profile retain separate authorization.
+`INFO`, `DEBUG` levels. The LCKFB XiaoTai development project defaults to
+`DEBUG`, which prints complete HTTP, MQTT and TiRTC/WHIP inputs and results,
+including authorization values. Switching to `INFO` suppresses those complete
+network payloads. Handle DEBUG output as sensitive development data. Downloads,
+account access, flashing, erasing, factory-partition changes and publishing a
+reusable board profile retain separate authorization.

package/skills/tirtc-beken-builder/VERSION

@@ -1 +1 @@
-0.11.1
+0.11.2

package/skills/tirtc-beken-builder/references/lckfb-bk7258-lessons.md

@@ -141,12 +141,11 @@ Require a host contract test plus artifact-bound HIL. At minimum verify:
   connect/confirmation timeouts and late-callback rejection;
 - minimum/largest internal heap during DTLS, camera and full-duplex overlap.
 
-Use conventional `ERROR`, `WARN`, `INFO`, `DEBUG` levels. The checked-in release
-configuration defaults to `INFO`; at that level log failures, recovery and state
-transitions but not complete network inputs or responses. An explicitly enabled
-`DEBUG` build prints complete HTTP, MQTT and TiRTC/WHIP inputs and results,
-including authorization values, so developers can reproduce protocol failures.
+Use conventional `ERROR`, `WARN`, `INFO`, `DEBUG` levels. The checked-in
+development configuration defaults to `DEBUG` and prints complete HTTP, MQTT
+and TiRTC/WHIP inputs and results, including authorization values, so developers
+can reproduce protocol failures. Switching to `INFO` logs failures, recovery and
+state transitions but not complete network inputs or responses.
 Contract tests must keep those full-payload format strings behind `BK_LOGD` or
 an equivalent DEBUG guard and reject them at INFO/WARN/ERROR. Treat DEBUG logs as
-sensitive development artifacts, keep them out of source control and restore
-INFO before producing release firmware.
+sensitive development artifacts and keep them out of source control.

package/skills/tirtc-beken-builder/references/tirtc-integration.md

@@ -60,7 +60,7 @@ documentation is context, not a substitute for the binary's build contract.
 
 Use `ERROR` for failed operations that cannot continue, `WARN` for degraded or
 recoverable behavior, `INFO` for lifecycle/state summaries, and `DEBUG` for wire
-diagnostics. Default product builds to INFO. At DEBUG, log complete HTTP method,
+diagnostics. The LCKFB development profile defaults to DEBUG. At DEBUG, log complete HTTP method,
 URL, headers, body and response; MQTT connect/subscribe/publish/receive fields and
 payloads; and TiRTC/WHIP descriptors, authorization values, callback results and
 generation identifiers. At INFO and above, do not print those complete network

package/skills/tirtc-esp32-builder/VERSION

@@ -1 +1 @@
-0.11.1
+0.11.2