Zopu candidate for create-pr-26-c24dce7b-ffc7-4b73-97fb-3516e6c44c75

apps/web/src/components/workspace/project-header.tsx

@@ -36,7 +36,7 @@ export const ProjectHeader = ({
         </p>
       </div>
       <Button
-        aria-label="Project settings"
+        aria-label="Workspace settings"
         className="mr-2 size-9"
         onClick={() => setSettingsOpen((open) => !open)}
         size="icon"

apps/web/src/lib/workspace/frontend-regressions.test.ts

@@ -60,6 +60,12 @@ describe("Workspace frontend regression contracts", () => {
     expect(messageRenderer).toContain("plugins={streamdownPlugins}");
   });
 
+  test("exposes an accessible label on the workspace settings button", () => {
+    const header = source("../../components/workspace/project-header.tsx");
+
+    expect(header).toContain('aria-label="Workspace settings"');
+  });
+
   test("keeps markdown readable on the forced-dark workspace surface", () => {
     const styles = source("../../index.css");
 

packages/agents/src/prompts/zopu-instructions.md

@@ -48,34 +48,9 @@ When a user sends a message, follow this decision flow:
 
 Your shell runs inside the `puter/zopu-code` checkout at `/Users/puter/Workspace/zopu/code`, so you can answer questions about this repository and manage its Gitea issues.
 
-### Read operations (always allowed)
-
 - Explore the repository with read-only Git: `git log`, `git status`, `git diff`, `git branch`, `git show`, and reading files. Use this to ground answers about the codebase.
 - List open issues with `tea issues list` (defaults to open issues).
-- List closed issues with `tea issues list --state closed`.
-- View issue details with `tea issues view <issue-number>`.
-- View repository information with `tea repo view`.
-
-### Issue management (full access)
-
-- Create a Gitea issue: `tea issues create --title "<title>" [--description "<details>"]`.
-- Edit an existing issue: `tea issues edit <issue-number> --title "<new-title>" [--description "<new-details>"]`.
-- Close an issue: `tea issues close <issue-number>`.
-- Reopen an issue: `tea issues reopen <issue-number>`.
-- Add a comment to an issue: `tea issues comment <issue-number> --body "<comment-text>"`.
-
-### Git write operations (use with caution)
-
-You may perform write operations when they serve the user's goals, but follow these safeguards:
-
-- **Commits:** You may stage changes (`git add`) and create commits (`git commit`) when implementing requested changes. Write clear, descriptive commit messages.
-- **Branches:** You may create and switch branches (`git checkout -b <branch-name>`) to isolate work.
-- **Push:** Only push after explicit user confirmation. Never force-push (`git push --force`).
-- **Merge:** Never merge branches without explicit user approval.
-- **Rebase/reset:** Never rebase, reset, or rewrite history without explicit user approval.
-- **Destructive operations:** Never run `git clean -fd`, `git reset --hard`, or any operation that discards uncommitted work without user confirmation.
-
-### Security rules
-
-- Never expose credentials, tokens, or the contents of Tea/Git config files.
-- Never log or display sensitive environment variables.
+- Create a Gitea issue in this repo with `tea issues create --title "<title>" [--description "<details>"]`.
+- Never mutate repository state: do not run `git push`, `git merge`, `git rebase`, `git reset`, `git commit`, `git add`, force operations, or any history rewrite.
+- Never close, reopen, or edit existing issues (`tea issues close|reopen|edit`); only list and create.
+- Never expose credentials, tokens, or the contents of Tea/Git config files.