GuanLdong aab77517c1 Ship unified note workflows with a stable Hub Note protocol ... This release unifies dated notes and related notes behind the HubNote model, adds timeline rendering improvements, and locks the note metadata contract into a single parser/writer path so future note sources can extend it safely. Constraint: Obsidian releases must stay within main.js, manifest.json, and styles.css while preserving legacy note frontmatter compatibility Rejected: Separate protocol docs without code/test enforcement | too easy for future changes to drift Rejected: Hard migration of legacy note files | unnecessary release risk for existing vaults Confidence: high Scope-risk: moderate Reversibility: clean Directive: Any future Hub Note YAML change must go through src/hubNotes.ts and docs/superpowers/specs/2026-07-11-hub-note-protocol.zh-CN.md Tested: npm run typecheck; npm test -- --runInBand; npm run build; npm run smoke; npm run release:assets; synced build to test vault with cmp checks Not-tested: Real Obsidian manual interaction verification after syncing 0.3.83 into the test vault		2026-07-11 22:57:46 +08:00
..
plans	Ship unified note workflows with a stable Hub Note protocol	2026-07-11 22:57:46 +08:00
specs	Ship unified note workflows with a stable Hub Note protocol	2026-07-11 22:57:46 +08:00