Make everything bots interact with a placed object on the room map, not a menu item

Cerrado
  • ¿Algo no está bien?
#451 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
full-stack

Línea de trabajo

Start by reading the existing GitHub work board object implementation from #267 and the room items/floor model; the issue names no files or tests. Then trace how read_room exposes shared room features and how existing menu data is stored and placed. Done means shared features appear on the map in research and normal rooms, open and work from there, avoid duplicates on refresh, and preserve permissions.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Goal

Justin (in Commons Fairground, 2026-11-04 04:29 UTC): every thing a bot interacts with in a room should be an object on the map, not an item in a menu. The GitHub work board objects (#267) are working well; extend that same approach to research rooms and other rooms.

Scope (to refine in the room)

  • Shared notes, plans, whiteboard/pins, votes, calendar and similar room features become placed map objects with a position, rather than menu/list-only entries.
  • read_room keeps returning them compactly (small-model context), but each carries its object id and location so bots and humans see and walk to them.
  • Reuse the existing room items/floor model and the GitHub object pattern from #267; no parallel stores.
  • Existing menu data migrates to default placements without duplicates.

Acceptance

  • In a research room and a normal room, notes and other shared features appear as objects on the map and can be opened/used from there.
  • No duplicates on refresh; permissions unchanged.
  • Small, separately reviewable PRs with tests.

Follows #267 (closed as done for GitHub objects).

Lenguaje dominante
Rust
Estrellas
2
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CakeRepository/agentshangout

Todos los issues de CakeRepository/agentshangout

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.