diff --git a/doc/bugs/git-annex__58_____60__stdout__62____58___hPutBuf__58___resource_vanished/comment_3_eaa0748eed9398ba59d49b3387ac4a82._comment b/doc/bugs/git-annex__58_____60__stdout__62____58___hPutBuf__58___resource_vanished/comment_3_eaa0748eed9398ba59d49b3387ac4a82._comment
new file mode 100644
index 0000000000..413b654eb7
--- /dev/null
+++ b/doc/bugs/git-annex__58_____60__stdout__62____58___hPutBuf__58___resource_vanished/comment_3_eaa0748eed9398ba59d49b3387ac4a82._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="pierreay"
+ avatar="http://cdn.libravatar.org/avatar/c1c640f9f581daaf2d9dedff2b84b614"
+ subject="comment 3"
+ date="2025-05-26T19:38:41Z"
+ content="""
+Thank you @joey and @mak for the hints.
+I was unable (even with strace) for chase down the particular system call that cause the issue, since it is highly random and generated by my shell prompt.
+However, mak seems right about the git_status module of starship. I increased my timeout from 500ms (default) to 1000ms (and will try slightly larger value if needed).
+If this mitigate the issue correctly, I will not comment anymore! But I suspect it to work. ;)
+"""]]
diff --git a/doc/bugs/keeps_trying_to_commit_file_unlocked/comment_7_4b0662ed3467cd46c3332d52ad30cef4._comment b/doc/bugs/keeps_trying_to_commit_file_unlocked/comment_7_4b0662ed3467cd46c3332d52ad30cef4._comment
new file mode 100644
index 0000000000..43e189ac52
--- /dev/null
+++ b/doc/bugs/keeps_trying_to_commit_file_unlocked/comment_7_4b0662ed3467cd46c3332d52ad30cef4._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 7"
+ date="2025-05-27T10:57:18Z"
+ content="""
+FTR, Yukai reported that it was \"WSL (Ubuntu 22.04, x86_64) on Windows 10. Git version was 2.34.1, git-annex version was 10.20230407-1~ndall+1.\".  So definitely not a trivial/typical setup ;)  I do not remember when it was that I have tried git-annex under WSL.
+"""]]
diff --git a/doc/bugs/proot_info__58___vpid_1__58___terminated_with_signal_4.mdwn b/doc/bugs/proot_info__58___vpid_1__58___terminated_with_signal_4.mdwn
new file mode 100644
index 0000000000..9bad084bec
--- /dev/null
+++ b/doc/bugs/proot_info__58___vpid_1__58___terminated_with_signal_4.mdwn
@@ -0,0 +1,46 @@
+### Please describe the problem.
+I get this error when I try to run git annex sync on my amazon fire tablet.
+`proot info: vpid 1: terminated with signal 4`
+
+```
+$ cat /proc/cpuinfo
+processor	: 0
+Processor	: ARMv7 Processor rev 3 (v7l)
+model name	: ARMv7 Processor rev 3 (v7l)
+BogoMIPS	: 32.19
+Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm aes pmull sha1 sha2 crc32 
+CPU implementer	: 0x41
+CPU architecture: 7
+CPU variant	: 0x0
+CPU part	: 0xd03
+CPU revision	: 3
+
+processor	: 1
+Processor	: ARMv7 Processor rev 3 (v7l)
+model name	: ARMv7 Processor rev 3 (v7l)
+BogoMIPS	: 26.00
+Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm aes pmull sha1 sha2 crc32 
+CPU implementer	: 0x41
+CPU architecture: 7
+CPU variant	: 0x0
+CPU part	: 0xd03
+CPU revision	: 3
+
+Hardware	: MT8163
+Revision	: 0000
+Serial		: 84b2d1e8651995fc
+```
+
+`uname -m` reports `armv7l`
+
+If I do `proot-distro login debian` then I can use the very same git-annex.linux and it works but it's slow (idk why). If I try to use git annex from termux then it fails with that error. Not that it matters, I'm using termux from here https://sourceforge.net/projects/android-ports-for-gnu-emacs/files/termux/ which is "a version of the Termux terminal emulator signed with
+Emacs's signing keys" so that Emacs can use the termux binaries or something.
+ 
+### What version of git-annex are you using? On what operating system?
+Android 9. LineageOS.
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+
+So, I've been trying to uss it for years. Kind of like how I tried using Emacs and went bankrupt twice before things clicked. I was so hung up on the symlinks. Then I finally understood some things, thanks Gemini, and now I'm using annex.addunlocked and annex.thin and I feel really nerdy and cool. I would love to get this working on my tablet too.
+
+Thanks!
diff --git a/doc/forum/What_does___34__upgrade__34___in_the_webapp_do__63__.mdwn b/doc/forum/What_does___34__upgrade__34___in_the_webapp_do__63__.mdwn
new file mode 100644
index 0000000000..abaa2f63d3
--- /dev/null
+++ b/doc/forum/What_does___34__upgrade__34___in_the_webapp_do__63__.mdwn
@@ -0,0 +1,3 @@
+The webapp showed "(metadata only)" behind a repository. Running `git annex upgrade` in the repositories didn't change that. I had top to "upgrade" the repository under "edit" in the webapp to fix that.
+
+What did upgrading in the webapp do, that running `git annex upgrade` did not?
diff --git a/doc/forum/tell_assistant_to_wait_5_mins_before_commiting__63__/comment_4_26bd8ac09928b5d9bf5eec2f254a8520._comment b/doc/forum/tell_assistant_to_wait_5_mins_before_commiting__63__/comment_4_26bd8ac09928b5d9bf5eec2f254a8520._comment
new file mode 100644
index 0000000000..c7738312d5
--- /dev/null
+++ b/doc/forum/tell_assistant_to_wait_5_mins_before_commiting__63__/comment_4_26bd8ac09928b5d9bf5eec2f254a8520._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="jnkl"
+ avatar="http://cdn.libravatar.org/avatar/2ab576f3bf2e0d96b1ee935bb7f33dbe"
+ subject="comment 4"
+ date="2025-05-26T15:30:01Z"
+ content="""
+Thank you very much!
+"""]]