<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-memory.git/project_doot_google_tasks_oauth_limitation.md, branch main</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.terst.org/claude-memory.git/atom?h=main</id>
<link rel='self' href='https://git.terst.org/claude-memory.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.terst.org/claude-memory.git/'/>
<updated>2026-08-15T18:06:00+00:00</updated>
<entry>
<title>Merge titanium's diverged memory tree into the shared history</title>
<updated>2026-08-15T18:06:00+00:00</updated>
<author>
<name>Claude Code</name>
<email>claude@terst.org</email>
</author>
<published>2026-08-15T18:06:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.terst.org/claude-memory.git/commit/?id=a6d58e009efcc06e7b5221d75ebed36533786dce'/>
<id>urn:sha1:a6d58e009efcc06e7b5221d75ebed36533786dce</id>
<content type='text'>
Titanium and tungsten had grown two separate, unreconciled memory sets
for the same -workspace scope. Ports over 18 titanium-only entries
(12 claudomator files, the fork-scope-creep lesson, the doot Google
Tasks OAuth limitation, the default-subagent-driven-execution
preference, scout's Facebook priority, Hawaii GIS endpoints), merges
two true duplicates into their existing tungsten files rather than
keeping parallel copies (the migration-rename incident -- same
022-&gt;023 rename, same commit, titanium's version added the
confirmed-safe-to-patch-prod-directly carve-out tungsten's didn't
have; the APK build OOM note, folded into project_doot_widget_build.md
as a RAM-constrained-host fallback), and marks
doot_future_task_scheduling_ideas.md as historical now that all four
of its backlog items (budgets, labels/projects, buckets, chains) are
built.
</content>
</entry>
</feed>
