[good first issue]🎯 docs: config comments disagree with actual defaults — l2DelayAfterL1Seconds off by 9x

[MuBeiGe]

Summary

Three config fields in the source have comments that disagree with the actual code defaults.

Field	Comment says	Actual default
maxScenes	default: 20	?? 15
l2DelayAfterL1Seconds	default: 90	?? 10
report.enabled	default: true	?? false

Impact

l2DelayAfterL1Seconds is off by 9x (comment says 90 seconds, code uses 10). Users who rely on the comment to understand pipeline timing will have incorrect mental model. For example, expecting a 90-second delay between L1 and L2 processing when the actual delay is only 10 seconds.

Evidence

Seen in v0.3.6 src/ source comments vs dist/index.mjs actual ?? fallback values.

Suggested Fix

Update the source comments to match the actual defaults (or update defaults to match comments, whichever the maintainers intended).

[Maxwell-Code07]

Thanks for the code audit! We've received your report about config comments disagreeing with actual defaults and will review it internally. We'll get back to you once we have results. Appreciate the attention to documentation accuracy!

[Maxwell-Code07]

We've selected this issue as 🎯 Good First Issue — perfect for new contributors to get started!

Task Details

Field	Content
Type	Feature
Difficulty	Low
Estimated Effort	2 days
Acceptance Criteria	1. Compare and fix 3 inconsistencies between comments and actual defaults (maxScenes: comment 20 → actual 15, l2DelayAfterL1Seconds: comment 90 → actual 10, report.enabled: comment true → actual false); 2. Add consistency tests between comments and defaults

Questions welcome! 🚀

[fei121]

I have joined the TencentDB Agent Memory Open Source Co-creation Program and claimed this issue.