From 3f9d2448e53a71633d7ee66d3aa03138ebb7c040 Mon Sep 17 00:00:00 2001 From: shinyobjectz Date: Fri, 13 Nov 2026 09:04:33 -0800 Subject: [PATCH] docs/scene-feed.feature SF8e: done. raea-feed #10 merged with raea-skills #58 (collaborate.md's row, reference/feed.md regenerated) and raea pins it (#133); the strict skills check passes against raea-feed main. The scene feed ships in 0.1.3 --- docs/scene-feed.feature | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/scene-feed.feature b/docs/scene-feed.feature index 55c1588e..2acad036 100644 --- a/docs/scene-feed.feature +++ b/docs/scene-feed.feature @@ -283,9 +283,12 @@ Feature: Scene: a feed item that is raea 3D looked at from inside And each comment in a scene tells the agent its point in the scene's space, the part and where it is written Rule: SF8. Open + # Status 11-13: SF8e done for 0.1.3 (Shane: the scene feed ships in 0.1.3, not 0.1.4). raea-feed #10 merged + # (24b2eb5) with raea-skills #58 (faa9938: collaborate.md's row, reference/feed.md regenerated), and raea pins it + # (#133, 2cb213634); SKILLS_STRICT=1 tools/skills.sh check passes against the app at raea-feed main. + @done Scenario: SF8e. Taught to agents # feed_post's type list is in the generated skills reference. Teaching `scene` is a change to raea-skills # (skills/raea/collaborate.md's "When you need to..." table, and reference/feed.md regenerated), which is public - # and merges by PR: it goes with the merge of raea-feed's branch scene, at Shane's word. Until then L1 is - # untouched, since raea-feed main has not changed + # and merges by PR, with the merge of raea-feed's branch scene Then the raea skill says when to post a scene and what the person can do with it