Repository navigation
feat: independent Broca publication bundle - #19
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepare an independent Broca Pages repository from a local data directory without copying the framework or private setup files. The new publication command previews by default and creates only a board, shared feed and minimal Pages workflow in a new destination. Board work links use the configured canonical repository.
Closes #18.
Scripts Changed
broca/publication.py: validated three-file publication bundle and repository-bound workflow.broca/__main__.py,broca/board.py: publication CLI and explicit board work destination.tests/test_publication.py: generated workflow execution, tampered artifact rejection, source preservation and output-boundary coverage.docs/publication.md,docs/setup.md,README.md: review/deployment/connection procedure.Validation
64 tests pass, including execution of the generated workflow artifact guard. Existing owner check validates 4 assistants and 18 records; live-default board/feed render passes. Diff whitespace and author review pass. No independent review claimed.
Limits
No remote creation, upload or deployment. An actual destination and visibility review remain required. The allowlist excludes raw files but is not a privacy scanner for rendered content. Output must be new; interrupted writes are inspected and regenerated into another new directory. No lifecycle/pause UI or upgrade support is claimed.
Tier: judge — merge mode: human /prm.
Heart RED development authorization
For this next task, the user answered the explicit Heart RED continuation request
with "conitnue", then approved the concrete implementation plan: "yeah I approve, go".
Authorization is task-specific development through PR-open, with human /prm retained.
Exact current RED reasons (unchanged):
Branch validation: 64 tests passed; existing owner check (4 assistants, 18 records)
and board/feed render passed; author diff/whitespace review passed. No independent
review claimed. No release, actual independent deployment or merge is authorized.